Tools & Wizards About Us
sauv.net screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

sauv.net

Sauver les lettres

Page Load Speed

2.4 sec in total

First Response

492 ms

Resources Loaded

1.5 sec

Page Rendered

408 ms

sauv.net screenshot

About Website

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.net

Key Findings

We analyzed Sauv.net page load time and found that the first response time was 492 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

sauv.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value1.0 s

100/100

10%

Network Requests Diagram

sauv.net

492 ms

commun.js

225 ms

presentation.js

257 ms

commun-screen2.css

263 ms

NJcYNfcktTA

202 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 62% of them (13 requests) were addressed to the original Sauv.net, 14% (3 requests) were made to S.ytimg.com and 10% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (492 ms) belongs to the original domain Sauv.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.6 kB (61%)

Content Size

48.5 kB

After Optimization

18.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sauv.net main page is 48.5 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. HTML takes 20.3 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 13.9 kB

  • Original 20.3 kB
  • After minification 15.8 kB
  • After compression 6.5 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. This page needs HTML code to be minified as it can gain 4.5 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.9 kB or 68% of the original size.

Image Optimization

-7%

Potential reduce by 637 B

  • Original 9.7 kB
  • After minification 9.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. Sauv images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 5.8 kB

  • Original 7.6 kB
  • After minification 6.3 kB
  • After compression 1.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 5.8 kB or 76% of the original size.

CSS Optimization

-86%

Potential reduce by 9.3 kB

  • Original 10.8 kB
  • After minification 6.0 kB
  • After compression 1.5 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. Sauv.net needs all CSS files to be minified and compressed as it can save up to 9.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (28%)

Requests Now

18

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sauv. 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 as a result speed up the page load time.

Network Requests Diagram

sauv.net

sauv.net

492 ms

commun.js

commun.js

225 ms

presentation.js

presentation.js

257 ms

commun-screen2.css

commun-screen2.css

263 ms

NJcYNfcktTA

NJcYNfcktTA

202 ms

bk.jpg

bk.jpg

116 ms

sllp.gif

sllp.gif

121 ms

plantu1.jpg

plantu1.jpg

119 ms

sll1.jpg

sll1.jpg

197 ms

sauver_titre.gif

sauver_titre.gif

286 ms

bt.gif

bt.gif

214 ms

ballpink.gif

ballpink.gif

237 ms

date_info.gif

date_info.gif

236 ms

www-embed-player-vfl5foy2V.css

www-embed-player-vfl5foy2V.css

106 ms

www-embed-player.js

www-embed-player.js

137 ms

base.js

base.js

210 ms

commun-print.css

commun-print.css

98 ms

9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js

9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js

120 ms

ad_status.js

ad_status.js

127 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

127 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

139 ms

Accessibility Review

sauv.net accessibility score

57

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

sauv.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

sauv.net SEO score

80

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

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 it matches the claimed language. Our system also found out that Sauv.net 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.

Social Sharing Optimization

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: