Your Website Score is

Similar Ranking

88
WIKIPEDIA
wikipedia.org
88
BOT OR NOT?
expedia.com
88
LEARNING TOOLS AND FLASHCARDS - FOR FREE! | QUIZLET
quizlet.com
88
YAHOO VIỆT NAM | TIN TỨC, TÀI CHÍNH VÀ GIẢI TRÍ
yahoo.com
88
哔哩哔哩 (゜-゜)つロ 干杯~-BILIBILI
bilibili.com
88
GOOGLE
google.pt
88
SMART LINKS FOR MUSIC MARKETING, ARTIST PROMOTION, AND FAN ENGAGEMENT | LINKFIRE
cyndilauper.lnk.to

Latest Sites

19
SENILE TEAM DEV LOG
senileteam.com
14
BOXHERO.IN
boxhero.in
21
HUYCHESS
huychess.sbs
96
YOUTUBE
youtu.be
9
YOUTUBE
youtube.com
19
YUPPOW - FREE HD MOVIES AND TV SHOWS STREAMING ONLINE
yuppow.org
14
-
coloressence.com

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
jQuery
JavaScript Frameworks
CloudFlare
CDN
PHP
Programming Languages
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
WordPress
CMS

88 nfe.prefeitura.sp.gov.br Last Updated: 3 years

Success 55% of passed verification steps
Warning 15% of total warning
Errors 30% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 91%
Best Practices Desktop Score 92%
SEO Desktop Score 70%
PWA Desktop Score 0%
Performance Mobile Score 80%
Best Practices Mobile Score 83%
SEO Mobile Score 58%
PWA Mobile Score 0%
Page Authority Authority 49%
Domain Authority Domain Authority 90%
Moz Rank 4.9/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: ISO-8859-1
Title Tag 20 Characters
NOTA DO MILHãO
Meta Description 0 Characters
NO DATA
Effective URL 43 Characters
https://nfe.prefeitura.sp.gov.br/login.aspx
Excerpt Page content
Nota do Milhão   Versão...
Keywords Cloud Density
ãµes1 gerais1 notã­cias1 contato1 informaã1 prestadores1 vindo1 participar1 sorteios1 lista1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
ãµes 1
gerais 1
notã­cias 1
contato 1
informaã 1
prestadores 1
vindo 1
participar 1
sorteios 1
lista 1
Google Preview Your look like this in google search result
NOTA DO MILHãO
https://nfe.prefeitura.sp.gov.br/login.aspx
Nota do Milhão   Versão...
Robots.txt File Detected
http://nfe.prefeitura.sp.gov.br/robots.txt
Sitemap.xml File Detected
http://nfe.prefeitura.sp.gov.br/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~18.83 KB
Code Size: ~11.29 KB
Text Size: ~7.54 KB Ratio: 40.02%

Social Data

Estimation Traffic and Earnings

136,281
Unique Visits
Daily
252,119
Pages Views
Daily
$243
Income
Daily
3,815,868
Unique Visits
Monthly
7,185,392
Pages Views
Monthly
$6,075
Income
Monthly
44,155,044
Unique Visits
Yearly
84,711,984
Pages Views
Yearly
$64,152
Income
Yearly

Desktop

Desktop Screenshot
Avoids an excessive DOM size 172 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minimizes main-thread work 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy 15 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Minify JavaScript Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoids enormous network payloads Total size was 259 KiB
Large network payloads cost users real money and are highly correlated with long load times
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused JavaScript Potential savings of 41 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Time to Interactive 0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 13 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Serve images in next-gen formats Potential savings of 70 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Efficiently encode images Potential savings of 30 KiB
Optimized images load faster and consume less cellular data
Keep request counts low and transfer sizes small 24 requests • 259 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce initial server response time Root document took 1,220 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 610 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Mobile

Mobile Screenshot
Speed Index 6.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids an excessive DOM size 172 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Efficiently encode images Potential savings of 30 KiB
Optimized images load faster and consume less cellular data
Total Blocking Time 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Reduce initial server response time Root document took 1,200 ms
Keep the server response time for the main document short because all other requests depend on it
Keep request counts low and transfer sizes small 24 requests • 259 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.2 s
First Contentful Paint marks the time at which the first text or image is painted
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoids enormous network payloads Total size was 259 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint 3.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 3.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Eliminate render-blocking resources Potential savings of 1,950 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Serve images in next-gen formats Potential savings of 70 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
First Contentful Paint (3G) 6306 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimizes main-thread work 1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 3.2 s
First Meaningful Paint measures when the primary content of a page is visible
Serve static assets with an efficient cache policy 15 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce unused JavaScript Potential savings of 41 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Minify JavaScript Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid chaining critical requests 13 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links
First 3 Links Relationship HTTP Status
https://nfe.prefeitura.sp.gov.br Internal Link 302
Lista de prestadores Internal Link 301
CLICANDO AQUI Internal Link 301

Alexa Rank

7,516

Global Rank

176

Brazil
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
nfe.prefeitura.sp.gov.co Available
nfe.prefeitura.sp.gov.us Available
nfe.prefeitura.sp.gov.com Available
nfe.prefeitura.sp.gov.org Already Registered
nfe.prefeitura.sp.gov.net Already Registered
ne.prefeitura.sp.gov.br Available
hfe.prefeitura.sp.gov.br Available
ufe.prefeitura.sp.gov.br Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 5754
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Vary: Accept-Encoding
Set-Cookie: ASP.NET_SessionId=pgotc1f1yeie1cffk32ya41i; path=/; HttpOnly; SameSite=Lax
Strict-Transport-Security: max-age=63072000; includeSubDomains
X-Frame-Options: sameorigin
X-Content-Type-Options: nosniff
Expect-CT: enforce, max-age=86400
Content-Security-Policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' https://fonts.googleapis.com https://fonts.gstatic.com;
X-OneAgent-JS-Injection: true
X-ruxit-JS-Agent: true
Server-Timing: dtSInfo;desc="1"
Set-Cookie: dtCookie=v_4_srv_10_sn_BB4139720FF8440D7AC20C091E92EEC5_perc_100000_ol_0_mul_1_app-3Adb66c4a801656e04_0; Path=/; Domain=.sp.gov.br
Date: Mon, 10 Oct 2022 16:32:31 GMT
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A nfe.prefeitura.sp.gov.br 177.22.132.191 IN 15
NS nfe.prefeitura.sp.gov.br dns4as.prodam.sp.gov.br IN 10800
NS nfe.prefeitura.sp.gov.br dns1as.prodam.sp.gov.br IN 10800
NS nfe.prefeitura.sp.gov.br dns2as.prodam.sp.gov.br IN 10800
NS nfe.prefeitura.sp.gov.br dns3as.prodam.sp.gov.br IN 10800

About Us

We provide SEO metrics for your website. There are many who have trusted on us and improved their position thanks to our recommendations

Contact Info

RYIN
10407 Feeney Trafficway Apt. 577
Maryland Line
1-760-992-3170
[email protected]

Follow Us

Facebook
© Copyright 2023
Languages | English