1.8 sec in total
475 ms
1 sec
273 ms
Welcome to sauv.net homepage info - get ready to check Sauv best content for France right away, or after learning these important things about sauv.net
Site du collectif Sauver les lettres
Visit sauv.netWe analyzed Sauv.net page load time and found that the first response time was 475 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
sauv.net performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value1.0 s
100/100
25%
Value1.4 s
100/100
10%
Value0 ms
100/100
30%
Value0.017
100/100
15%
Value1.0 s
100/100
10%
475 ms
80 ms
154 ms
156 ms
115 ms
Our browser made a total of 15 requests to load all elements on the main page. We found that all of those requests were addressed to Sauv.net and no external sources were called. The less responsive or slowest element that took the longest time to load (475 ms) belongs to the original domain Sauv.net.
Page size can be reduced by 19.6 kB (46%)
42.6 kB
23.0 kB
In fact, the total size of Sauv.net main page is 42.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. Only 10% of websites need less resources to load. HTML takes 28.6 kB which makes up the majority of the site volume.
Potential reduce by 18.0 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 18.0 kB or 63% of the original size.
Potential reduce by 637 B
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. Sauv images are well optimized though.
Potential reduce by 168 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 813 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. Sauv.net needs all CSS files to be minified and compressed as it can save up to 813 B or 32% of the original size.
We found no issues to fix!
14
14
The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sauv. According to our analytics all requests are already optimized.
sauv.net
475 ms
commun.js
80 ms
presentation.js
154 ms
commun-screen2.css
156 ms
bk.jpg
115 ms
sllp.gif
114 ms
TerreDesLettres.gif
308 ms
plantu1.jpg
157 ms
sll1.jpg
157 ms
sauver_titre.gif
163 ms
bt.gif
165 ms
ballpink.gif
166 ms
droite.gif
234 ms
date_info.gif
234 ms
commun-print.css
78 ms
sauv.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
sauv.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
sauv.net 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 uses legible font sizes
Tap targets are not sized appropriately
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sauv.net can be misinterpreted by Google and other search engines. Our service has detected that French 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 Sauv.net 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.
sauv.net
Open Graph description is not detected on the main page of Sauv. 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: