Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

saponaire.com

Savons, baumes, cosmétiques, produits de soins Nature & Progrès

Page Load Speed

3.3 sec in total

First Response

334 ms

Resources Loaded

2.8 sec

Page Rendered

222 ms

saponaire.com screenshot

About Website

Welcome to saponaire.com homepage info - get ready to check Saponaire best content right away, or after learning these important things about saponaire.com

Savonnerie Saponaire, savons, baumes à lèvres, cosmétiques, produits de soins et ménagers à base d'ingédients biologiques, fait artisanalement à la main, certifiés Nature & Progrès.

Visit saponaire.com

Key Findings

We analyzed Saponaire.com page load time and found that the first response time was 334 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

saponaire.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value16,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.482

17/100

15%

TTI (Time to Interactive)

Value26.3 s

0/100

10%

Network Requests Diagram

saponaire.com

334 ms

www.saponaire.com

379 ms

598 ms

v_28_3dc6b290a101290f1630d4539f9e64e9_all.css

149 ms

css

26 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 74% of them (23 requests) were addressed to the original Saponaire.com, 6% (2 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Saponaire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 461.0 kB (38%)

Content Size

1.2 MB

After Optimization

748.1 kB

In fact, the total size of Saponaire.com main page is 1.2 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. 50% of websites need less resources to load. Images take 635.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.7 kB

  • Original 37.1 kB
  • After minification 37.1 kB
  • After compression 9.4 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 27.7 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 12.4 kB

  • Original 635.0 kB
  • After minification 622.6 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. Saponaire images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 182.0 kB

  • Original 256.0 kB
  • After minification 256.0 kB
  • After compression 74.0 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 182.0 kB or 71% of the original size.

CSS Optimization

-85%

Potential reduce by 239.0 kB

  • Original 281.0 kB
  • After minification 237.3 kB
  • After compression 42.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. Saponaire.com needs all CSS files to be minified and compressed as it can save up to 239.0 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saponaire. According to our analytics all requests are already optimized.

Accessibility Review

saponaire.com accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

saponaire.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

saponaire.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saponaire.com 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 Saponaire.com 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Saponaire. 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: