2.3 sec in total
220 ms
1.5 sec
588 ms
Welcome to tempo.terra.com.br homepage info - get ready to check Tempo Terra best content for Brazil right away, or after learning these important things about tempo.terra.com.br
Descubra o clima e a previsão do tempo atual para a sua localização. Informações precisas e em tempo real você encontra na Climatempo. Clique e conheça!
Visit tempo.terra.com.brWe analyzed Tempo.terra.com.br page load time and found that the first response time was 220 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
tempo.terra.com.br performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value4.8 s
31/100
25%
Value15.2 s
1/100
10%
Value12,350 ms
0/100
30%
Value0.025
100/100
15%
Value33.0 s
0/100
10%
220 ms
112 ms
53 ms
79 ms
182 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tempo.terra.com.br, 33% (34 requests) were made to Climatempo.com.br and 18% (18 requests) were made to Img.climatempo.com.br. The less responsive or slowest element that took the longest time to load (652 ms) relates to the external source Img.climatempo.com.br.
Page size can be reduced by 1.1 MB (44%)
2.6 MB
1.5 MB
In fact, the total size of Tempo.terra.com.br main page is 2.6 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 230.9 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 230.9 kB or 78% of the original size.
Potential reduce by 58.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. Tempo Terra images are well optimized though.
Potential reduce by 715.5 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 715.5 kB or 71% of the original size.
Potential reduce by 125.4 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. Tempo.terra.com.br needs all CSS files to be minified and compressed as it can save up to 125.4 kB or 85% of the original size.
Number of requests can be reduced by 50 (51%)
99
49
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tempo Terra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and as a result speed up the page load time.
tempo.terra.com.br
220 ms
www.climatempo.com.br
112 ms
default.css
53 ms
modernizr.js
79 ms
contentpar.js
182 ms
jquery.min.js
107 ms
foundation.min.js
106 ms
foundation.dependencies.js
53 ms
main.js
86 ms
tickerme.min.js
86 ms
require.js
87 ms
mtm.js
10 ms
analytics.js
18 ms
AVCwEMDHnLGmu4aQtkex
203 ms
553fbf3149d63e8c3fa34838.js
24 ms
collect
25 ms
module-uaparser.js
3 ms
201602040000d.js
134 ms
pageviewspar.js
494 ms
mqdefault.jpg
254 ms
ico-play-bar.png
103 ms
chamada-mapas.jpg
200 ms
selo-de-previsao.jpg
199 ms
plugin-wordpress.jpg
200 ms
videos-de-previsao.jpg
199 ms
poweredbyterra.png
200 ms
mqdefault.jpg
209 ms
mqdefault.jpg
308 ms
mqdefault.jpg
307 ms
mqdefault.jpg
306 ms
climatempo.woff
256 ms
beacon.js
137 ms
atrk.js
158 ms
pql
238 ms
gpt.js
141 ms
t3m.js
372 ms
gw.js
232 ms
async_player.js
202 ms
show
173 ms
t3m.js
287 ms
pasoka.js
151 ms
303x142_2c775acb53d264a868c9286d91be0f51.png
439 ms
126x126_11a93ff21fb893b282fdc426dcf20ea8.png
472 ms
126x126_5bfd4b377902231da6336a8ec067ef11.png
539 ms
126x126_c2e0636ff32a4c17fed319790ac034bd.png
516 ms
196x196_999981a2da63b480b84e02ab7a3de1c9.png
603 ms
196x196_448c52936f21fff6ff053aee4cab7082.png
603 ms
196x196_db10bb6230ccdd795470762a9708d3e6.png
602 ms
303x142_0fbcb5f1dcd182dccc01fd4e587957b8.png
532 ms
303x142_e31e6769e7cc189811813a64b27d13b6.png
609 ms
303x142_fdcb42b0fcc09206569513fc6d1c4200.png
610 ms
303x142.jpg
608 ms
145x108_9e735eaa99551d312f8c2938d177cc50.png
609 ms
145x108_32181c24e8c6a02b73b0db4b8adafbb7.jpg
619 ms
145x108_306b26e61d93e572af20db6f19e2662f.png
608 ms
145x108_0392287a4c631ffd42fed70b55be6ff4.png
652 ms
145x108_08b6eb9a267faf6d4b9bde3708f4ebb0.jpg
641 ms
145x108_07885b2ea6095a28145251d9e9dc169d.jpg
640 ms
145x108_212f38b8cf123e4e42d8050bbced1624.png
640 ms
bn_radarSP.jpg
118 ms
bn_radarRJ.jpg
117 ms
pubads_impl_82.js
9 ms
atrk.gif
200 ms
rta.js
172 ms
ads
376 ms
container.html
120 ms
test.png
313 ms
logo_boostbox.png
143 ms
banner_header_element.png
62 ms
loading.gif
78 ms
banner_search_button.png
81 ms
706357341.js
55 ms
page_load
226 ms
event
110 ms
page_load
218 ms
json.js
29 ms
text.js
41 ms
config.json
31 ms
Index.js
37 ms
collect
9 ms
Cookie.js
34 ms
Favorite.js
36 ms
Search.js
40 ms
SelectBuilder.js
41 ms
Portal.js
41 ms
Geo.js
35 ms
Live.js
67 ms
CurrentWeather.js
67 ms
expansion_embed.js
30 ms
ads
47 ms
osd.js
21 ms
15876139949712268704
67 ms
abg.js
79 ms
m_js_controller.js
101 ms
googlelogo_color_112x36dp.png
54 ms
muitas-nuvensN.jpg
72 ms
ads
216 ms
3330223866652845982
73 ms
s
44 ms
x_button_blue2.png
34 ms
busca-estados
38 ms
busca-cidades-uf
124 ms
tempo.terra.com.br 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
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
[id] attributes on active, focusable elements are not unique
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 [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>).
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.
tempo.terra.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
tempo.terra.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 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 Tempo.terra.com.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 Tempo.terra.com.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.
tempo.terra.com.br
Open Graph data is detected on the main page of Tempo Terra. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: