7.4 sec in total
1.8 sec
5.4 sec
264 ms
Visit tempo1.cptec.inpe.br now to see the best up-to-date Tempo 1 Cptec INPE content for Brazil and also check out these interesting facts you probably never knew about tempo1.cptec.inpe.br
Previsão de Tempo - Brasília / DF - Centro de Previsão de Tempo e Estudos Climáticos - CPTEC/INPE - Ministério da Ciência, Tecnologia, Inovações e Comunicações - Brasil um país de todos
Visit tempo1.cptec.inpe.brWe analyzed Tempo1.cptec.inpe.br page load time and found that the first response time was 1.8 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tempo1.cptec.inpe.br performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value6.6 s
8/100
25%
Value9.0 s
14/100
10%
Value3,410 ms
2/100
30%
Value0.123
84/100
15%
Value18.8 s
3/100
10%
1782 ms
39 ms
562 ms
38 ms
144 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 13% of them (15 requests) were addressed to the original Tempo1.cptec.inpe.br, 44% (50 requests) were made to Img0.cptec.inpe.br and 13% (15 requests) were made to Mt0.google.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source S0.cptec.inpe.br.
Page size can be reduced by 373.5 kB (11%)
3.4 MB
3.0 MB
In fact, the total size of Tempo1.cptec.inpe.br main page is 3.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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 267.1 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 267.1 kB or 59% of the original size.
Potential reduce by 106.2 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. Tempo 1 Cptec INPE images are well optimized though.
Potential reduce by 62 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 91 B
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. Tempo1.cptec.inpe.br has all CSS files already compressed.
Number of requests can be reduced by 12 (12%)
103
91
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tempo 1 Cptec INPE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
tempo1.cptec.inpe.br
1782 ms
font-awesome.min.css
39 ms
app.css
562 ms
ol.css
38 ms
polyfill.min.js
144 ms
ol.js
55 ms
popper.min.js
56 ms
app.js
836 ms
js
159 ms
224.png
1104 ms
gview
85 ms
criterios-avisos-meteorologicos.pdf
831 ms
criterios-previsao-probabilistica.pdf
966 ms
titulo_wrf_24.png
423 ms
imagem.jpg
1764 ms
previsao.html
544 ms
centroeste.html
422 ms
nordeste.html
553 ms
norte.html
412 ms
sudeste.html
545 ms
sul.html
417 ms
valedoparaiba.html
414 ms
superficie_atual.gif
1646 ms
desc_satelite.html
416 ms
legenda.html
564 ms
prev24h_2017102600.gif
1786 ms
prev48h_2017102600.gif
1651 ms
prev72h_2017102600.gif
1653 ms
prev96h_2017102600.gif
1655 ms
prev120h_2017102600.gif
1557 ms
escala_WRF_ANA_sem_fundo.png
407 ms
analisesinotica.png
546 ms
legenda_sinoticaN.jpg
1926 ms
cptec.png
281 ms
bg-acess-key.gif
154 ms
sprite.png
280 ms
diversidade.png
281 ms
nascer-sol.png
279 ms
por-sol.png
283 ms
voltar-topo.png
373 ms
wrf_prev24horas.png
3056 ms
opensans-400-webfont.woff
494 ms
opensans-800-webfont.woff
494 ms
fontawesome-webfont.woff
17 ms
opensans-700-webfont.woff
352 ms
lyrs=m&hl=en&x=5&y=9&z=4
26 ms
lyrs=m&hl=en&x=5&y=8&z=4
36 ms
lyrs=m&hl=en&x=5&y=10&z=4
52 ms
lyrs=m&hl=en&x=6&y=9&z=4
40 ms
lyrs=m&hl=en&x=6&y=8&z=4
41 ms
lyrs=m&hl=en&x=4&y=9&z=4
42 ms
lyrs=m&hl=en&x=4&y=8&z=4
40 ms
lyrs=m&hl=en&x=5&y=7&z=4
42 ms
lyrs=m&hl=en&x=5&y=6&z=4
53 ms
lyrs=m&hl=en&x=6&y=10&z=4
52 ms
lyrs=m&hl=en&x=4&y=10&z=4
54 ms
lyrs=m&hl=en&x=6&y=7&z=4
55 ms
lyrs=m&hl=en&x=6&y=6&z=4
53 ms
lyrs=m&hl=en&x=4&y=7&z=4
54 ms
lyrs=m&hl=en&x=4&y=6&z=4
71 ms
min_pn.png
1285 ms
marcador2.gif
931 ms
marcador.gif
789 ms
estilo_tempo_texto.css
148 ms
marcador.gif
163 ms
ec.png
1224 ms
ci.png
1232 ms
c.png
1234 ms
in.png
1237 ms
pp.png
1277 ms
cm.png
1363 ms
cn.png
1365 ms
pt.png
1369 ms
pm.png
1371 ms
np.png
1374 ms
pc.png
1414 ms
pn.png
1499 ms
cv.png
1501 ms
ch.png
1506 ms
t.png
1508 ms
ps.png
1511 ms
e.png
1551 ms
n.png
1636 ms
nv.png
1639 ms
g.png
1643 ms
ne.png
1646 ms
nd.png
1647 ms
pnt.png
1688 ms
psc.png
1772 ms
pcm.png
1776 ms
pct.png
1780 ms
pcn.png
1782 ms
npt.png
1785 ms
npn.png
1825 ms
opensans-bold.woff
232 ms
js
47 ms
analytics.js
21 ms
collect
58 ms
collect
39 ms
ga-audiences
90 ms
ncn.png
913 ms
nct.png
831 ms
ncm.png
829 ms
npm.png
829 ms
npp.png
829 ms
vn.png
829 ms
ct.png
826 ms
ppn.png
827 ms
ppt.png
830 ms
ppm.png
829 ms
nppc.png
828 ms
nppcm.png
830 ms
nppct.png
826 ms
nppcn.png
827 ms
tempo1.cptec.inpe.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
[role]s are not contained by their required parent element
[aria-*] attributes are not valid or misspelled
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
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 valid value for its [lang] attribute.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
tempo1.cptec.inpe.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
tempo1.cptec.inpe.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 doesn't use 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 Tempo1.cptec.inpe.br 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 Tempo1.cptec.inpe.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.
tempo1.cptec.inpe.br
Open Graph description is not detected on the main page of Tempo 1 Cptec INPE. 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: