Sapo.pt - SEO Checker - Website Review

Your Website Score is

Similar Ranking

A PIPOCA MAIS DOCE

apipocamaisdoce.sapo.pt

HOTMART: APRENDA O QUE QUISER, ENSINE O QUE SOUBER

go.hotmart.com

SAPO

sapo.pt

Latest Sites

FREDERICO LOPES - WORDPRESS SEO

fredericolopes.com

HOME - ATMOSFERASTORE

atmosferastore.com

INDEX OF /

ceramileao.com

DUDEK PORTUGAL – ASAS DUDEK

dudek.pt

FOTOGRAFIAS, APENAS

fotografiasapenas.blogspot.pt

CAIXIPRONTO – ALUMÍNIOS E PVC

caixipronto.pt

VIDEOLIGHT - VIDEO PORTEIRO, TELEFONES DE PORTA, E INTERCOMUNICADORES

videolight.pt

Top Technologies

PHP

Programming Languages

Google Font API

Font Scripts

WordPress

CMS

Apache

Web Servers

Font Awesome

Font Scripts

Nginx

Web Servers

jQuery

JavaScript Frameworks

Yoast SEO

SEO

WooCommerce

Ecommerce

Google Tag Manager

Tag Managers

91 sapo.pt Last Updated: 3 weeks

Success 54% of passed verification steps

Warning 23% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 94%

Best Practices Desktop Score 86%

SEO Desktop Score 83%

Progressive Web App Desktop Score 30%

Performance Mobile Score 49%

Best Practices Mobile Score 86%

SEO Mobile Score 82%

Progressive Web App Mobile Score 32%

Page Authority Authority 63%

Domain Authority Domain Authority 93%

Moz Rank 6.3/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 4 Characters

SAPO

Meta Description 157 Characters

Portal SAPO.PT: notícias de Portugal e do mundo, desporto, capas dos jornais, mail, são só o início. Descubra mais todos os dias.

Effective URL 19 Characters

https://www.sapo.pt

Excerpt Page content

SAPO SAPO Início ...

Keywords Cloud Density

sapo60 mais34 para33 lisboa15 jornal14 lifestyle13 desporto12 grupo11 porto11 egor10

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

Keyword	Freq	Title	Desc	Domain	H1	H2
sapo	60
mais	34
para	33
lisboa	15
jornal	14
lifestyle	13
desporto	12
grupo	11
porto	11
egor	10

Google Preview Your look like this in google search result

SAPO

https://www.sapo.pt

Portal SAPO.PT: notícias de Portugal e do mundo, desporto, capas dos jornais, mail, são só o início. Descubra mais todos o

Robots.txt File Detected

http://sapo.pt/robots.txt

Sitemap.xml File Detected

http://sapo.pt/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: 2020-02-11 / 11 months 21 days

MEO - SERVIÇOS DE COMUNICAÇÕES E MULTIMÉDIA S.A.

Admin Email: gestao.dominios@telecom.pt

Nameservers

ns2.sapo.pt

IPv4:

212.55.154.194

and

IPv6:

dns01.sapo.pt

IPv4:

213.13.28.116

and

IPv6:

2001:8a0:2106:4:213:13:28:116

dns02.sapo.pt

IPv4:

213.13.30.116

and

IPv6:

2001:8a0:2206:4:213:13:30:116

ns.sapo.pt

IPv4:

212.55.154.202

and

IPv6:

Page Size Code & Text Ratio

Document Size: ~535.98 KB

Code Size: ~493.94 KB

Text Size: ~42.03 KB Ratio: 7.84%

Social Data

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

PWA - Manifest

SAPO SAPO

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)

Param name

SAPO

Param display

browser

Param start_url

/?homescreen

Param short_name

SAPO

Param theme_color

#69A618

Desktop

Enable text compression Potential savings of 4 KiB

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

Speed Index 1.4 s

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

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

Total Blocking Time 30 ms

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

Keep request counts low and transfer sizes small 93 requests • 1,426 KiB

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

Largest Contentful Paint 1.1 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Minify JavaScript Potential savings of 2 KiB

Minifying JavaScript files can reduce payload sizes and script parse time

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

Time to Interactive 2.2 s

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

Properly size images Potential savings of 126 KiB

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

Remove unused JavaScript Potential savings of 290 KiB

Remove unused JavaScript to reduce bytes consumed by network activity

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

Avoid serving legacy JavaScript to modern browsers Potential savings of 56 KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers

Eliminate render-blocking resources Potential savings of 0 ms

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

Max Potential First Input Delay 110 ms

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

First CPU Idle 2.1 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/).

Avoid chaining critical requests 10 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 large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

Avoids enormous network payloads Total size was 1,426 KiB

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

Minimizes main-thread work 2.0 s

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

JavaScript execution time 0.5 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

Remove unused CSS Potential savings of 57 KiB

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 116 KiB

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

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 an excessive DOM size 4,257 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)

Cumulative Layout Shift 0.044

Cumulative Layout Shift measures the movement of visible elements within the viewport

Avoid long main-thread tasks 5 long tasks 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 23 resources found

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

Avoids large JavaScript libraries with smaller alternatives 0 large libraries found

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

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

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

First Meaningful Paint 0.9 s

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

Initial server response time was short Root document took 330 ms

Keep the server response time for the main document short because all other requests depend on it

First Contentful Paint 0.9 s

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

Mobile

Avoids enormous network payloads Total size was 1,256 KiB

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

Estimated Input Latency 70 ms

Eliminate render-blocking resources Potential savings of 530 ms

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

Avoid long main-thread tasks 20 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

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

Cumulative Layout Shift 0.068

Cumulative Layout Shift measures the movement of visible elements within the viewport

Tap targets are not sized appropriately 60% 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

Serve images in next-gen formats Potential savings of 116 KiB

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

Avoid an excessive DOM size 4,022 elements

Defer offscreen images Potential savings of 2 KiB

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

Document uses legible font sizes 98.96% 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

Speed Index 3.5 s

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

Page load is not fast enough on mobile networks Interactive at 12.8 s

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

Properly size images Potential savings of 116 KiB

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

Total Blocking Time 1,000 ms

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

Serve static assets with an efficient cache policy 17 resources found

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

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

Enable text compression Potential savings of 4 KiB

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

Reduce JavaScript execution time 2.1 s

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

Minimize main-thread work 6.4 s

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

Minify JavaScript Potential savings of 2 KiB

Minifying JavaScript files can reduce payload sizes and script parse time

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

Remove unused JavaScript Potential savings of 261 KiB

Remove unused JavaScript to reduce bytes consumed by network activity

Initial server response time was short Root document took 160 ms

Keep the server response time for the main document short because all other requests depend on it

Time to Interactive 12.8 s

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

First Contentful Paint 2.1 s

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

Largest Contentful Paint 4.4 s

Largest Contentful Paint marks the time at which the largest text or image is painted

First Meaningful Paint 2.1 s

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

Avoid chaining critical requests 10 chains found

First Contentful Paint (3G) 4410 ms

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

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

Remove unused CSS Potential savings of 58 KiB

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

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

Avoid serving legacy JavaScript to modern browsers Potential savings of 38 KiB

First CPU Idle 8.7 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/).

Keep request counts low and transfer sizes small 78 requests • 1,256 KiB

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

Avoids large JavaScript libraries with smaller alternatives 0 large libraries found

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

Max Potential First Input Delay 320 ms

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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

99,999,999

Global Rank

99,999,999

Traffic

Search

Domain Available

Domain (TDL) and Typo	Status
sapo.co	Already Registered
sapo.us	Already Registered
sapo.com	Already Registered
sapo.org	Already Registered
sapo.net	Already Registered
spo.pt	Already Registered
wapo.pt	Available Buy Now!
xapo.pt	Already Registered

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
Date: Mon, 04 Jan 2021 19:28:26 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 66615
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block
Referrer-Policy: no-referrer-when-downgrade
Feature-Policy: microphone 'none' ; camera 'none' ;
Content-Security-Policy: default-src https: blob: ; script-src https: blob: 'unsafe-inline' 'unsafe-eval'; style-src https: 'unsafe-inline' ; img-src https: data: ; media-src blob: https: ; upgrade-insecure-requests; block-all-mixed-content; connect-src https: wss://messaging.insurads.com;
Content-Encoding: gzip
X-Server: Kalahari
X-Server-RequestTime: "0.001000"
X-NCache: hit
Strict-Transport-Security: max-age=31536000
X-Content-Type-Options: nosniff
Content-Security-Policy: upgrade-insecure-requests; block-all-mixed-content
Referrer-Policy: origin-when-cross-origin

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	sapo.pt	213.13.146.142	IN	57
NS	sapo.pt	dns01.sapo.pt	IN	162
NS	sapo.pt	ns.sapo.pt	IN	162
NS	sapo.pt	ns2.sapo.pt	IN	162
NS	sapo.pt	dns02.sapo.pt	IN	162
MX	sapo.pt	mx.ptmail.sapo.pt	IN	20
TXT	sapo.pt	google-site-verification=xVGdeOf_JlKH3UWPXLWuk0dNvGdTtgL6RqDYIgXAtoM	IN	300
TXT	sapo.pt	mtc=MDVkMTYzNGEtNGVmNy00ZDllLWE3NmMtN2RkN2U5MDg2N2Zk	IN	300
TXT	sapo.pt	v=spf1 include:_spf.sapo.pt ~all	IN	300

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

91 sapo.pt Last Updated: 3 weeks

Desktop

Mobile

Social Data

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Sign up for see all features and reviews about this site

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

99,999,999

99,999,999

Domain Available

Information Server

About Us

Contact Info

Follow Us