Prefeitura.sp.gov.br - SEO Checker

Your Website Score is

Similar Ranking

ФЕДЕРАЛЬНАЯ НАЛОГОВАЯ СЛУЖБА

nalog.ru

L'EXPRESS - ACTUALITÉS POLITIQUE, MONDE, ECONOMIE ET CULTURE - L'EXPRESS

lexpress.fr

ENTREPRENEUR - START, RUN AND GROW YOUR BUSINESS.

entrepreneur.com

THE DAILY BEAST

thedailybeast.com

SKY SPORTS - SPORTS NEWS, TRANSFERS, SCORES | WATCH LIVE SPORT

skysports.com

HOWSTUFFWORKS - LEARN HOW EVERYTHING WORKS!

howstuffworks.com

HOME | GLOBAL | SIEMENS

siemens.com

Latest Sites

THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ

noithatmanhhe.vn

SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP

nhacanhothongminh.com

CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM

crypto-mining.biz

99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING

999dice.com

RELANDICE BOT FOR 999DICE

relandice.com

❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !

baophong.vn

ONE MORE STEP

seeking.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

90 prefeitura.sp.gov.br Last Updated: 10 months

Success 55% of passed verification steps

Warning 15% of total warning

Errors 30% of total errors, require fast action

Mobile

Performance Desktop Score 75%

Best Practices Desktop Score 62%

SEO Desktop Score 73%

Progressive Web App Desktop Score 15%

Performance Mobile Score 36%

Best Practices Mobile Score 62%

SEO Mobile Score 75%

Progressive Web App Mobile Score 41%

Page Authority Authority 50%

Domain Authority Domain Authority 92%

Moz Rank 5.0/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 36 Characters

PREFEITURA DE SÃO PAULO — PREFEITURA

Meta Description 0 Characters

NO DATA

Effective URL 28 Characters

http://www.capital.sp.gov.br

Excerpt Page content

Prefeitura de São Paulo — Prefeitura Acesso à informação ...

Keywords Cloud Density

municipal20 conselho13 paulo13 para12 município9 coordenação8 negócios7 cidade6 especial6 serviços6

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
municipal	20
conselho	13
paulo	13
para	12
município	9
coordenação	8
negócios	7
cidade	6
especial	6
serviços	6

Google Preview Your look like this in google search result

PREFEITURA DE SÃO PAULO — PREFEITURA

http://www.capital.sp.gov.br

Prefeitura de São Paulo — Prefeitura Acesso à informação ...

Robots.txt File Detected

http://prefeitura.sp.gov.br/robots.txt

Sitemap.xml File Detected

http://prefeitura.sp.gov.br/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Updated: 1970-01-01 / 51 years

Create on: 1970-01-01 / 51 years

Expires on: 1970-01-01 / 617 months 21 days

Cia Proc. de Dados do Estado de S Paulo - Prodesp ,BR BR

Registrar Email: [email protected]

Nameservers

dns1e.sp.gov.br

200.144.6.154

dns3e.sp.gov.br

200.144.6.92

dns2e.sp.gov.br

201.55.16.39

Page Size Code & Text Ratio

Document Size: ~78.77 KB

Code Size: ~50.29 KB

Text Size: ~28.48 KB Ratio: 36.16%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Reduce server response times (TTFB) Root document took 1,150 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,190 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 26 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Reduce the impact of third-party code Third-party code blocked the main thread for 260 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

Total Blocking Time 90 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.7 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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

Properly size images Potential savings of 7 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 2.6 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 1.9 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 1,978 KB

Large network payloads cost users real money and are highly correlated with long load times

robots.txt is not valid 1 error found

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed

Minimizes main-thread work 1.3 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.2 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 19 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

Avoid an excessive DOM size 928 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)

Minify JavaScript Potential savings of 2 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 1.3 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 96 requests • 1,978 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 45 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 110 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 2.1 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.3 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 10 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Minify CSS Potential savings of 10 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 88 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 271 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Does not use HTTPS 68 insecure requests found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

User Timing marks and measures 3 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Mobile

Max Potential First Input Delay 420 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 9.3 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

First Contentful Paint (3G) 8363 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Estimated Input Latency 110 ms

Minify CSS Potential savings of 10 KB

Minifying CSS files can reduce network payload sizes

Tap targets are not sized appropriately 80% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 89.29% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 92 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 271 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Does not use HTTPS 68 insecure requests found

User Timing marks and measures 3 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Server response times are low (TTFB) Root document took 470 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 3,650 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 26 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Reduce the impact of third-party code Third-party code blocked the main thread for 1,280 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

Total Blocking Time 940 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 2.4 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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

Defer offscreen images Potential savings of 130 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 6.6 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 8.6 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 2,034 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 4.2 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

robots.txt is not valid 1 error found

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed

First Contentful Paint 4.2 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 19 chains found

Avoid an excessive DOM size 915 elements

Minify JavaScript Potential savings of 2 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 4.4 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 91 requests • 2,034 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 44 resources found

A long cache lifetime can speed up repeat visits to your page

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Server: nginx/1.12.2
Date: Mon, 09 Dec 2019 04:21:02 GMT
Content-Type: text/html;charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
X-Cache-Operation: plone.app.caching.weakCaching
X-RAMCache: plone.app.caching.operations.ramcache
Content-Language: pt-br
Expires: Fri, 11 Dec 2009 03:15:28 GMT
ETag: W/"||1022991|pt-br|0|Sunburst Theme|0|0|1553175814.46"
X-Ua-Compatible: IE=edge,chrome=1
Cache-Control: max-age=0, must-revalidate, private
X-Cache-Rule: plone.content.folderView
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=15768000; includeSubDomains
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Security-Policy-Report-Only: default-src 'self'; img-src *; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval'
X-Proxy-Cache: EXPIRED
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	prefeitura.sp.gov.br	177.22.129.167	IN	230
NS	prefeitura.sp.gov.br	dns1as.prodam.sp.gov.br	IN	86331
NS	prefeitura.sp.gov.br	dns3as.prodam.sp.gov.br	IN	86331
NS	prefeitura.sp.gov.br	dns2as.prodam.sp.gov.br	IN	86331
NS	prefeitura.sp.gov.br	dns4as.prodam.sp.gov.br	IN	86331
MX	prefeitura.sp.gov.br	mx4as.prodam.sp.gov.br	IN	180
MX	prefeitura.sp.gov.br	mx0as.prodam.sp.gov.br	IN	180
TXT	prefeitura.sp.gov.br	v=spf1 a:mxsend.prodam.sp.gov.br a:mxsend1as.prodam.sp.gov.br a:mxsend2as.prodam.sp.gov.br a:mxsend6as.prodam.sp.gov.br ~all	IN	180
TXT	prefeitura.sp.gov.br	MS=ms29524692	IN	10800

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

90 prefeitura.sp.gov.br Last Updated: 10 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

jQuery

Nginx

Plone

Python

YouTube

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments