5.2 sec in total
1.1 sec
3.9 sec
235 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.1 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
tempo1.cptec.inpe.br performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value8.8 s
1/100
25%
Value13.3 s
2/100
10%
Value16,750 ms
0/100
30%
Value0.116
85/100
15%
Value31.1 s
0/100
10%
1087 ms
39 ms
421 ms
418 ms
34 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 37% of them (23 requests) were addressed to the original Tempo1.cptec.inpe.br, 25% (16 requests) were made to Img0.cptec.inpe.br and 17% (11 requests) were made to Cptec.inpe.br. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cptec.inpe.br.
Page size can be reduced by 239.0 kB (26%)
931.6 kB
692.6 kB
In fact, the total size of Tempo1.cptec.inpe.br main page is 931.6 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. 30% of websites need less resources to load. Javascripts take 322.1 kB which makes up the majority of the site volume.
Potential reduce by 93.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. 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.8 kB or 36% of the original size.
Potential reduce by 9.4 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 113.8 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 113.8 kB or 35% of the original size.
Potential reduce by 22.0 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. Tempo1.cptec.inpe.br needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 79% of the original size.
Number of requests can be reduced by 23 (41%)
56
33
The browser has sent 56 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 6 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
tempo1.cptec.inpe.br
1087 ms
jquery-1.7.1.min.js
39 ms
jquery.colorbox.js
421 ms
abas_funcoes.js
418 ms
css
34 ms
colorbox.css
425 ms
tempo_tarja.css
472 ms
logos.css
807 ms
headerCPTEC.js
1896 ms
barra.js
766 ms
urchin.js
5 ms
br1.jpg
1127 ms
seta_esq.gif
213 ms
ic_outono.gif
188 ms
ic_inverno.gif
373 ms
ic_primavera.gif
421 ms
ic_verao.gif
422 ms
br2.jpg
1124 ms
br3.jpg
1249 ms
br4.jpg
1250 ms
br5.jpg
1259 ms
br6.jpg
1256 ms
img_atu_nova.jpg
1318 ms
superficie_aba.gif
1671 ms
ps.png
1458 ms
n.png
1460 ms
c.png
1464 ms
pixel.gif
210 ms
seta_dir.gif
242 ms
seta.gif
212 ms
analisesinotica.png
951 ms
banner_semiarido.jpg
626 ms
seloweb.gif
416 ms
bol_cptec_ipmet.jpg
420 ms
bg_eti_izq.gif
417 ms
bg_eti_der.gif
462 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
26 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
27 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
27 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
28 ms
uBt6T9
35 ms
previsao.do
439 ms
logos_aplicativos.png
1087 ms
dg1.gif
585 ms
square3.gif
589 ms
background2.jpg
601 ms
bolsuperficie.shtml
790 ms
estilo_cookies.css
189 ms
pt.png
1208 ms
ponto_laranja.gif
188 ms
fundo_cookie2.gif
211 ms
estilo_tempo_texto.css
211 ms
__utm.gif
18 ms
overlay.png
213 ms
pa.cur
594 ms
controls.png
223 ms
border.png
237 ms
loading_background.png
221 ms
loading.gif
238 ms
min_ci.gif
210 ms
uv_13.0.gif
210 ms
min_pc.gif
212 ms
uv_14.0.gif
185 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
N/A
ISO-8859-1
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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tempo1.cptec.inpe.br main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
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: