Tools & Wizards About Us
sapo.io screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

sapo.io

Stratus CDN

Page Load Speed

3.8 sec in total

First Response

311 ms

Resources Loaded

3.3 sec

Page Rendered

196 ms

sapo.io screenshot

About Website

Welcome to sapo.io homepage info - get ready to check Sapo best content for Brazil right away, or after learning these important things about sapo.io

Stratus is a CDN that automatically caches your files, so they will be faster and closer to your visitors. It has great coverage in Portugal and some Portuguese speaking countries.

Visit sapo.io

Key Findings

We analyzed Sapo.io page load time and found that the first response time was 311 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

sapo.io performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

sapo.io

311 ms

sapo.io

387 ms

www.sapo.io

570 ms

style.min.css

761 ms

script.min.js

1399 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 11% of them (3 requests) were addressed to the original Sapo.io, 89% (25 requests) were made to C192168.cdn.sapo.io. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source C192168.cdn.sapo.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.8 kB (6%)

Content Size

452.4 kB

After Optimization

426.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Sapo.io main page is 452.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 394.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 15.8 kB

  • Original 19.4 kB
  • After minification 19.4 kB
  • After compression 3.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 394.6 kB
  • After minification 393.3 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Sapo images are well optimized though.

CSS Optimization

-23%

Potential reduce by 8.7 kB

  • Original 38.4 kB
  • After minification 38.4 kB
  • After compression 29.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Sapo.io needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 23% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

19

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sapo. According to our analytics all requests are already optimized.

Network Requests Diagram

sapo.io

sapo.io

311 ms

sapo.io

sapo.io

387 ms

www.sapo.io

www.sapo.io

570 ms

style.min.css

style.min.css

761 ms

script.min.js

script.min.js

1399 ms

slider_img1_small.jpg

slider_img1_small.jpg

1118 ms

slider_img2_small.jpg

slider_img2_small.jpg

1215 ms

slider_img3_small.jpg

slider_img3_small.jpg

1121 ms

logo_hp.png

logo_hp.png

1120 ms

logo_desporto.png

logo_desporto.png

1118 ms

logo_ink.png

logo_ink.png

1278 ms

logo_meokanal.png

logo_meokanal.png

1274 ms

logo_videos.png

logo_videos.png

1276 ms

logo_blogs.png

logo_blogs.png

1284 ms

logo_fotos.png

logo_fotos.png

1370 ms

logo_mail.png

logo_mail.png

1487 ms

madeby-149x54.png

madeby-149x54.png

1487 ms

logo_stratus.png

logo_stratus.png

709 ms

social.png

social.png

711 ms

Lato-Regular.woff

Lato-Regular.woff

831 ms

Lato-Light.woff

Lato-Light.woff

682 ms

Lato-Bold.woff

Lato-Bold.woff

798 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1044 ms

stratus_icons.woff

stratus_icons.woff

751 ms

slider_img1_large.jpg

slider_img1_large.jpg

546 ms

slider_img2_large.jpg

slider_img2_large.jpg

359 ms

slider_img3_large.jpg

slider_img3_large.jpg

575 ms

Lato-Black.woff

Lato-Black.woff

365 ms

Accessibility Review

sapo.io accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sapo.io best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

sapo.io SEO score

98

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sapo.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Sapo.io main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

sapo.io

Open Graph data is detected on the main page of Sapo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: