3.4 sec in total
462 ms
2.8 sec
165 ms
Welcome to sapo.tl homepage info - get ready to check SAPO best content for East Timor right away, or after learning these important things about sapo.tl
Atualidade, Saúde, Futebol, Finanças, Lifestyle, Famosos, Tecnologia, Local, Ambiente, Opinião, Jornais e Revistas, Promoções, Mail, Emprego e Carros.
Visit sapo.tlWe analyzed Sapo.tl page load time and found that the first response time was 462 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
sapo.tl performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value13.9 s
0/100
25%
Value8.1 s
21/100
10%
Value3,660 ms
1/100
30%
Value0
100/100
15%
Value16.5 s
5/100
10%
462 ms
204 ms
207 ms
212 ms
311 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 42% of them (38 requests) were addressed to the original Sapo.tl, 19% (17 requests) were made to Js.sapo.pt and 15% (14 requests) were made to Pub.sapo.pt. The less responsive or slowest element that took the longest time to load (845 ms) relates to the external source I.s.sl.pt.
Page size can be reduced by 165.2 kB (44%)
372.7 kB
207.5 kB
In fact, the total size of Sapo.tl main page is 372.7 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. 45% of websites need less resources to load. Javascripts take 178.7 kB which makes up the majority of the site volume.
Potential reduce by 25.4 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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.4 kB or 76% of the original size.
Potential reduce by 10.8 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.
Potential reduce by 129.0 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 129.0 kB or 72% of the original size.
Number of requests can be reduced by 55 (61%)
90
35
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SAPO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.sapo.tl
462 ms
reset.html5.css
204 ms
main.css
207 ms
widgets.css
212 ms
prototype.js
311 ms
334 ms
334 ms
332 ms
416 ms
416 ms
418 ms
419 ms
420 ms
515 ms
517 ms
517 ms
519 ms
sapo.js
326 ms
sapo.legacy.js
325 ms
local.legacy.js
301 ms
widgets.legacy.js
302 ms
lang.js
323 ms
195 ms
198 ms
287 ms
208 ms
02f9d843f30016471171cd027d43b4e6.gif
845 ms
pipe.gif
105 ms
frase.html
105 ms
afr.php
408 ms
ico_pa.png
106 ms
bg_btn.png
103 ms
bg_nav.png
103 ms
bg_h2_.png
104 ms
bg_nav_hover.png
197 ms
ico_feedback.png
200 ms
bg_nav_destaques_timorleste.png
207 ms
bg_tab_destaques.png
205 ms
bg_nav_destaques_timorleste_hover.png
206 ms
img_default.png
207 ms
bg_mapa.png
465 ms
balao_pt.png
301 ms
balao_ao.png
308 ms
balao_mz.png
309 ms
balao_cv.png
310 ms
balao_tl.png
311 ms
pub.png
465 ms
ico_mail.png
465 ms
ico_tempo.png
466 ms
ptl.gif
467 ms
30c07776b466966af6d41e8dcc6a0cd5.jpg
719 ms
c81162e2805d449c5e4a37a50bad3d79.jpg
824 ms
ae176c57490611ca6c2a1d79b5a41d32.jpg
721 ms
c7e3c39712f2b6bc7ba90d7e1e7c3434.jpg
722 ms
914a1d235de0fc07bce94870662d2062.jpg
721 ms
628 ms
afr.php
373 ms
mercado_iframe.html
440 ms
botao300x73.html
476 ms
ns.tl.html
474 ms
ico_info.png
476 ms
ajs.php
310 ms
like.php
113 ms
vpd1GgSCNsd.css
91 ms
M0DWM6a_9ro.css
107 ms
AdP_CKHZFBh.css
126 ms
_rx8naC75Dy.js
160 ms
TuuohdynnB6.js
144 ms
d6RcVOf4_V3.js
192 ms
phKJLmGTCBO.js
192 ms
f79117b7e941100c30c47a97d06b122e.jpg
731 ms
lg.php
107 ms
lg.php
109 ms
6daf171c7002d1aef46e7105d4a16d49.png
778 ms
lg.php
108 ms
Bw8qRoQ9D-v.js
19 ms
Xz08Qlfw8qz.js
52 ms
main.css
209 ms
106 ms
ajs.php
176 ms
ajs.php
172 ms
lg.php
115 ms
27e92902a2c6cc3504ffc0e53b706059.jpg
504 ms
lg.php
107 ms
70e65ff731628c41a91f3a8d9461b480.png
330 ms
ajs.php
112 ms
lg.php
107 ms
f9a425697379ebc73db61e41e183118a.png
213 ms
ajs.php
179 ms
5c2895ac44db6739aa2e7deb6872345f.png
315 ms
lg.php
108 ms
sapo.tl accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
sapo.tl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
sapo.tl SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sapo.tl can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Sapo.tl 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.
sapo.tl
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: