2.6 sec in total
1.2 sec
1.4 sec
0 ms
Visit wttr.in now to see the best up-to-date Wttr content for France and also check out these interesting facts you probably never knew about wttr.in
Visit wttr.inWe analyzed Wttr.in page load time and found that the first response time was 1.2 sec and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
wttr.in performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value3.5 s
65/100
25%
Value3.7 s
85/100
10%
Value150 ms
95/100
30%
Value0.001
100/100
15%
Value4.0 s
87/100
10%
1188 ms
99 ms
190 ms
56 ms
6 ms
Our browser made a total of 5 requests to load all elements on the main page. We found that 60% of them (3 requests) were addressed to the original Wttr.in, 20% (1 request) were made to Buttons.github.io and 20% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Wttr.in.
Page size can be reduced by 25.7 kB (83%)
30.9 kB
5.2 kB
In fact, the total size of Wttr.in main page is 30.9 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. 15% of websites need less resources to load. HTML takes 30.9 kB which makes up the majority of the site volume.
Potential reduce by 25.7 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 25.7 kB or 83% of the original size.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wttr. According to our analytics all requests are already optimized.
wttr.in
1188 ms
style.css
99 ms
stylesheet.css
190 ms
buttons.js
56 ms
widgets.js
6 ms
wttr.in accessibility score
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
wttr.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
wttr.in SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wttr.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wttr.in 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.
wttr.in
Open Graph description is not detected on the main page of Wttr. 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: