3.7 sec in total
352 ms
3.1 sec
260 ms
Click here to check amazing NTP content for Brazil. Otherwise, check out these important facts you probably never knew about ntp.br
Visit ntp.brWe analyzed Ntp.br page load time and found that the first response time was 352 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ntp.br performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value3.7 s
58/100
25%
Value7.8 s
23/100
10%
Value4,270 ms
1/100
30%
Value0.23
54/100
15%
Value18.0 s
3/100
10%
352 ms
537 ms
184 ms
338 ms
386 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 52% of them (37 requests) were addressed to the original Ntp.br, 18% (13 requests) were made to Relogio.ntp.br and 8% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ntp.br.
Page size can be reduced by 197.5 kB (14%)
1.4 MB
1.2 MB
In fact, the total size of Ntp.br main page is 1.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 23.8 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 6.4 kB, which is 21% 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 23.8 kB or 78% of the original size.
Potential reduce by 139.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. Obviously, NTP needs image optimization as it can save up to 139.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 32.9 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 32.9 kB or 14% of the original size.
Potential reduce by 1.8 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. Ntp.br has all CSS files already compressed.
Number of requests can be reduced by 12 (22%)
55
43
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NTP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
ntp.br
352 ms
ntp.br
537 ms
bootstrap.min.css
184 ms
theme.css
338 ms
all.css
386 ms
logo-nicbr-topo.png
382 ms
logo-cgibr-topo.png
383 ms
ntp2.png
384 ms
on-logo.png
446 ms
banner1.png
1193 ms
banner_ntp.jpg
1192 ms
relogio-seguro.jpg
910 ms
horario-de-verao.jpg
1192 ms
ntp-estrutura.png
939 ms
guias.png
909 ms
jquery-2.js
923 ms
bootstrap.min.js
932 ms
glight.php
717 ms
7PvZnbEwPzI
155 ms
cgi.png
938 ms
ntp.br
705 ms
blank
48 ms
88x31.png
78 ms
sobre.png
713 ms
ceptro-cidadao-na-rede.png
687 ms
ceptro-ipv6.png
934 ms
ceptro-simet.png
796 ms
ceptro-bcp.png
937 ms
ceptro-camada8.png
936 ms
ceptro-opencdn.png
943 ms
ceptro-inoc.png
941 ms
ceptro-medicoes.png
942 ms
footer.png
1197 ms
montserrat-bold-webfont.woff
1011 ms
montserrat-regular-webfont.woff
1150 ms
fa-brands-400.woff
1184 ms
glyphicons-halflings-regular.woff
1151 ms
raleway-bold-webfont.woff
1151 ms
raleway-extralight-webfont.woff
1157 ms
raleway-regular-webfont.woff
1226 ms
fa-solid-900.woff
1315 ms
fa-regular-400.woff
1184 ms
88x31.png
27 ms
www-player.css
9 ms
www-embed-player.js
31 ms
base.js
58 ms
ad_status.js
184 ms
vTEfc-jlr9e_tfMt-BR8Zcc1_6XGLRk25TFtjqWuknE.js
128 ms
embed.js
48 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
50 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
62 ms
id
24 ms
Create
112 ms
7PvZnbEwPzI
177 ms
blank
96 ms
style-light.css
227 ms
glight.css
485 ms
light.js
517 ms
Create
175 ms
id
19 ms
GenerateIT
259 ms
GenerateIT
72 ms
hora_certa.png
135 ms
twit_glight.png
183 ms
logo-ntpbr.png
135 ms
s.php
210 ms
s.php
203 ms
fundo.png
249 ms
ponteiro_seg.png
336 ms
ponteiro_hora.png
336 ms
ponteiro_min.png
575 ms
ntp.br 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
ntp.br 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
Page has valid source maps
ntp.br SEO score
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 Ntp.br 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 Ntp.br 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.
ntp.br
Open Graph description is not detected on the main page of NTP. 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: