Correios.com.br - SEO Checker

Your Website Score is

Similar Ranking

카카오

kakao.com

NEWS.COM.AU — AUSTRALIA’S #1 NEWS SITE

news.com.au

INÍCIO - INEP

inep.gov.br

CENTERS FOR DISEASE CONTROL AND PREVENTION

cdc.gov

LIVE, BREAKING NEWS TODAY: LATEST NATIONAL HEADLINES, WORLD NEWS AND MORE FROM CBSNEWS.COM AND WATCH THE CBSN LIVE NEWS STREAM 24X7

cbsnews.com

NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION | U.S. DEPARTMENT OF COMMERCE

noaa.gov

STOCK MARKETS, BUSINESS NEWS, FINANCIALS, EARNINGS - CNBC

cnbc.com

Latest Sites

i72tq6h2fsoku1o5.onion

MONTHJOB - GET PAID FOR SUBSCRIPTIONS WITH FREE NEWSLETTERS

monthjob.com

eurobux.biz

OFFICIAL SITE - ZAAPTV - MAAXTV - ARAABTV - AUSTRALIA & N.Z

globetv.com.au

GIFTS AUSTRALIA WILL HELP TO FIND THE BEST GIFT QUICKLY FOR EVERY OCCASION!

giftsaustralia.com.au

FAN+ OFFERS FANS ACCESS TO EXTRAORDINARY EXPERIENCES

fanplus.com

FURNITURE SHOP ONLINE IN AUSTRALIA | CHEAP & AFFORDABLE - DREAMO LIVING

dreamo.com.au

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

91 correios.com.br Last Updated: 2 years

Success 39% of passed verification steps

Warning 15% of total warning

Errors 46% of total errors, require fast action

Mobile

Performance Desktop Score 88%

Best Practices Desktop Score 69%

SEO Desktop Score 73%

Progressive Web App Desktop Score 38%

Performance Mobile Score 79%

Best Practices Mobile Score 69%

SEO Mobile Score 74%

Progressive Web App Mobile Score 37%

Page Authority Authority 58%

Domain Authority Domain Authority 93%

Moz Rank 5.8/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 84 Characters

CORREIOS: ENCOMENDAS, RASTREAMENTO, TELEGRAMAS, CEP, CARTAS, SELOS, AGÊNCIAS E MAIS!

Meta Description 0 Characters

NO DATA

Effective URL 22 Characters

http://correios.com.br

Excerpt Page content

Correios: encomendas, rastreamento, telegramas, cep, cartas, selos, agências e mais! Headmouse ...

Keywords Cloud Density

correios29 mais12 para12 atendimento8 serviços8 postal8 você7 prazos6 objetos6 precisa5

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

Keyword	Freq	Title	Desc	Domain	H1	H2
correios	29
mais	12
para	12
atendimento	8
serviços	8
postal	8
você	7
prazos	6
objetos	6
precisa	5

Google Preview Your look like this in google search result

CORREIOS: ENCOMENDAS, RASTREAMENTO, TELEGRAMAS, CEP, CARTAS,

http://correios.com.br

Correios: encomendas, rastreamento, telegramas, cep, cartas, selos, agências e mais! Headmouse ...

Robots.txt File Detected

http://correios.com.br/robots.txt

Sitemap.xml File No Found

http://correios.com.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 / 52 years

Create on: 1970-01-01 / 52 years

Expires on: 2028-10-30 / 88 months 9 days

Empresa Brasileira de Correios e Tel�grafos ,BR BR BR

Registrar Email: [email protected]

Nameservers

dns.correios.com.br

201.48.198.4

dns1.correios.com.br

201.48.198.5

dns2.correios.com.br

201.48.199.11

dns3.correios.com.br

201.48.199.14

Page Size Code & Text Ratio

Document Size: ~85.19 KB

Code Size: ~49.38 KB

Text Size: ~35.81 KB Ratio: 42.03%

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

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

Total Blocking Time 0 ms

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

JavaScript execution time 0.2 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 156 KB

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

Speed Index 2.0 s

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

First CPU Idle 0.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,900 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 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 0.9 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 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

Avoids an excessive DOM size 701 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 6 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.9 s

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

Keep request counts low and transfer sizes small 92 requests • 1,900 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

Max Potential First Input Delay 60 ms

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

Time to Interactive 1.0 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

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

Remove unused CSS Potential savings of 14 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 758 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 87 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

Reduce server response times (TTFB) Root document took 740 ms

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

Eliminate render-blocking resources Potential savings of 580 ms

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

Mobile

Does not use HTTPS 87 insecure requests found

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

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

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

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

Minimize third-party usage Third-party code blocked the main thread for 120 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 170 ms

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

JavaScript execution time 1.0 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 112 KB

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

Speed Index 5.1 s

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

First CPU Idle 3.5 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,900 KB

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

Minimize main-thread work 2.5 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 2.9 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 13 chains found

Avoids an excessive DOM size 705 elements

Minify JavaScript Potential savings of 6 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 3.0 s

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

Keep request counts low and transfer sizes small 92 requests • 1,900 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 31 resources found

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

Max Potential First Input Delay 270 ms

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

Time to Interactive 4.0 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) 5866.5 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 30 ms

Tap targets are not sized appropriately 63% 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 99.82% 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 14 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 758 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

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.6.0
Date: Tue, 26 Nov 2019 08:45:14 GMT
Content-Type: text/html;charset=utf-8
Content-Length: 12654
Connection: keep-alive
X-Cache-Operation: plone.app.caching.strongCaching
Content-Language: es
Content-Encoding: gzip
Expires: Tue, 26 Nov 2019 09:43:25 GMT
Vary: Accept-Encoding
X-Ua-Compatible: IE=edge,chrome=1
Cache-Control: max-age=7200, proxy-revalidate, public, private
X-Cache-Rule: plone.content.folderView
X-Frame-Options: SAMEORIGIN
Set-Cookie: serverid-SSVBR0299=SAC1236-03; path=/
Accept-Ranges: bytes
X-Varnish: 1325589805 1325541057
Age: 3291
Via: 1.1 varnish
X-Cache: HIT
X-Cache-Hits: 121
Set-Cookie: sitecorreioscookie-%3FEXTERNO%3Fpool_portalZP_80=AKBOKIMA; Expires=Tue, 26-Nov-2019 08:58:15 GMT; Path=/

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	correios.com.br	201.48.198.80	IN	7148
NS	correios.com.br	dns2.correios.com.br	IN	14399
NS	correios.com.br	dns1.correios.com.br	IN	14399
NS	correios.com.br	dns.correios.com.br	IN	14399
NS	correios.com.br	dns3.correios.com.br	IN	14399
MX	correios.com.br	mx1.correios.com.br	IN	14399
MX	correios.com.br	mx2.correios.com.br	IN	14399
TXT	correios.com.br	v=spf1 mx -all	IN	14399

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

91 correios.com.br Last Updated: 2 years

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

jQuery

Nginx

Plone

Python

Varnish

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