5.6 sec in total
357 ms
5 sec
244 ms
Click here to check amazing NOS content for Portugal. Otherwise, check out these important facts you probably never knew about nos.pt
Liga-te à rede 5G com os nossos tarifários móveis ou pacotes de Internet e televisão. Internet fixa e móvel, loja online com smartphones e muito mais.
Visit nos.ptWe analyzed Nos.pt page load time and found that the first response time was 357 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
nos.pt performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value18.7 s
0/100
25%
Value14.4 s
1/100
10%
Value3,830 ms
1/100
30%
Value0.297
40/100
15%
Value20.1 s
2/100
10%
357 ms
219 ms
135 ms
221 ms
326 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 61% of them (42 requests) were addressed to the original Nos.pt, 10% (7 requests) were made to Cdn.nos.pt and 7% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Webcare.byside.com.
Page size can be reduced by 1.2 MB (43%)
2.8 MB
1.6 MB
In fact, the total size of Nos.pt main page is 2.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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 184.0 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 184.0 kB or 86% of the original size.
Potential reduce by 19.7 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. NOS images are well optimized though.
Potential reduce by 754.3 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 754.3 kB or 73% of the original size.
Potential reduce by 243.3 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. Nos.pt needs all CSS files to be minified and compressed as it can save up to 243.3 kB or 86% of the original size.
Number of requests can be reduced by 35 (56%)
63
28
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NOS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
nos.pt
357 ms
particulares
219 ms
home.aspx
135 ms
screen.min.css
221 ms
init.js
326 ms
initstrings.js
217 ms
strings.js
338 ms
ie55up.js
347 ms
ScriptResource.axd
347 ms
blank.js
323 ms
ScriptResource.axd
345 ms
jquery-1.11.2.min.js
540 ms
jayscript.min.js
431 ms
modernizr.custom.js
433 ms
byside_webcare.js
859 ms
GoogleTagManagerColor.js
436 ms
WebResource.axd
449 ms
responsive-carousel.min.js
444 ms
responsive-carousel.addons.min.js
555 ms
stacktable.min.js
557 ms
picturefill.min.js
558 ms
jquery-ui-1.9.2.custom.min.js
779 ms
magnific.js
557 ms
jquery.responsiveTabs.min.js
640 ms
script.min.js
739 ms
instyler.min.js
640 ms
print.min.css
112 ms
323 ms
wtid.php
110 ms
nos.png
395 ms
arrow_back.png
119 ms
dropNplay.png
400 ms
drop_kanguru_janeiro.png
316 ms
Nos_telefone_drop.jpg
314 ms
drop_smartphones_natal.jpg
315 ms
Destaques-Dropdown.png
317 ms
AzoSansWeb-Regular.woff
474 ms
AzoSansWeb-Medium.woff
474 ms
AzoSansWeb-Light.woff
474 ms
AzoSansWeb-Bold.woff
475 ms
nosfont.svg
423 ms
nosfont.woff
420 ms
stat.php
466 ms
fbds.js
174 ms
gtm.js
167 ms
extra-large.png
802 ms
extra-large.png
578 ms
extra-large.png
273 ms
extra-large.png
682 ms
large.png
606 ms
large25.png
179 ms
large.png
383 ms
largehp.jpg
481 ms
large.png
496 ms
large.png
802 ms
usert_agent.php
2557 ms
analytics.js
33 ms
conversion_async.js
55 ms
190 ms
linkid.js
70 ms
113 ms
collect
64 ms
collect
29 ms
collect
48 ms
collect
84 ms
62 ms
collect
53 ms
ga-audiences
24 ms
ga-audiences
29 ms
nos.pt accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
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
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.
nos.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
nos.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nos.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nos.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.
nos.pt
Open Graph description is not detected on the main page of NOS. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: