7.3 sec in total
569 ms
6.7 sec
84 ms
Click here to check amazing Telecom content for Portugal. Otherwise, check out these important facts you probably never knew about telecom.pt
Atuamos de Portugal para o Mundo, investindo e intervindo em quatro dimensões fundamentais: Pessoas, Tecnologia, Inovação e Sustentabilidade.
Visit telecom.ptWe analyzed Telecom.pt page load time and found that the first response time was 569 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
telecom.pt performance score
name
value
score
weighting
Value16.0 s
0/100
10%
Value28.0 s
0/100
25%
Value23.3 s
0/100
10%
Value4,740 ms
0/100
30%
Value0.925
3/100
15%
Value30.3 s
0/100
10%
569 ms
233 ms
718 ms
125 ms
363 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 99% of them (73 requests) were addressed to the original Telecom.pt, 1% (1 request) were made to Js.sapo.pt. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Telecom.pt.
Page size can be reduced by 3.1 MB (36%)
8.8 MB
5.6 MB
In fact, the total size of Telecom.pt main page is 8.8 MB. 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. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 93.2 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 93.2 kB or 82% of the original size.
Potential reduce by 133.1 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. Telecom images are well optimized though.
Potential reduce by 2.3 MB
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 2.3 MB or 79% of the original size.
Potential reduce by 574.9 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. Telecom.pt needs all CSS files to be minified and compressed as it can save up to 574.9 kB or 87% of the original size.
Number of requests can be reduced by 56 (82%)
68
12
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Telecom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.telecom.pt
569 ms
VariationRoot.aspx
233 ms
en-us
718 ms
pagelayouts15.css
125 ms
corev15.css
363 ms
searchv15.css
579 ms
normalize.min.css
320 ms
default.css
743 ms
fix.css
543 ms
init.js
762 ms
html5.js
426 ms
jquery-1.11.2.min.js
590 ms
slick.min.js
644 ms
fileinput.js
655 ms
telecom.configuration.js
692 ms
taxonomy.helper.js
700 ms
telecom.helper.js
760 ms
jquery.spservices-2014.02.min.js
876 ms
translator.js
800 ms
jquery.cookie.js
811 ms
jquery-ui.min.js
1066 ms
displaytemplate.helper.js
862 ms
captcha.js
864 ms
telecom.validate.js
905 ms
telecom.search.js
922 ms
pagelayout.helper.js
974 ms
ScriptResource.axd
997 ms
blank.js
984 ms
ScriptResource.axd
1024 ms
sp.init.js
1040 ms
clientrenderer.js
1103 ms
ScriptResx.ashx
1104 ms
search.clientcontrols.js
1218 ms
search.cbs.js
1127 ms
item_slideshow.js
1151 ms
group_content.js
1171 ms
control_slideshow.js
1193 ms
item_news.js
1206 ms
449 ms
control_news.js
1231 ms
item_linkstelecom.js
1148 ms
control_linkstelecom.js
972 ms
item_highlight.js
942 ms
control_highlight.js
897 ms
ScriptResx.ashx
810 ms
sp.ui.dialog.js
779 ms
sp.runtime.js
798 ms
sp.js
876 ms
sp.taxonomy.js
782 ms
jquery.mobile.min.js
750 ms
lemon.js
761 ms
regua.js
707 ms
functions.js
721 ms
grid.js
782 ms
searchautocomplete.js
767 ms
main.js
768 ms
WebResource.axd
710 ms
favicon.ico
2612 ms
spcommon.png
2615 ms
logo-pt.png
2613 ms
logo-pt.png
2614 ms
sprite_button.png
2596 ms
sprite_social.png
2596 ms
OpenSans-Regular-webfont.woff
2595 ms
OpenSans-Semibold-webfont.woff
2595 ms
jquery.cookie.js
2579 ms
cookies.js
1325 ms
items
1326 ms
items
1326 ms
customstrings.js
115 ms
OpenSans-Bold-webfont.woff
139 ms
sprite_cookies.png
112 ms
initstrings.js
120 ms
print.css
110 ms
telecom.pt 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
telecom.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
telecom.pt 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
Image elements do not have [alt] attributes
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 Telecom.pt 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 Telecom.pt 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.
telecom.pt
Open Graph data is detected on the main page of Telecom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: