Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

sanoflore.net

sanoflore.net

Page Load Speed

4.1 sec in total

First Response

288 ms

Resources Loaded

3.7 sec

Page Rendered

77 ms

sanoflore.net screenshot

About Website

Welcome to sanoflore.net homepage info - get ready to check Sanoflore best content right away, or after learning these important things about sanoflore.net

This domain name has been registered with Gandi.net. It is currently parked by the owner.

Visit sanoflore.net

Key Findings

We analyzed Sanoflore.net page load time and found that the first response time was 288 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

sanoflore.net performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value20.7 s

0/100

10%

TBT (Total Blocking Time)

Value25,470 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value32.4 s

0/100

10%

Network Requests Diagram

sanoflore.net

288 ms

www.sanoflore.fr

1173 ms

82132999-f761-4723-a2b0-7788ee19f763.css

57 ms

common.css

586 ms

gabarit-home.css

285 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sanoflore.net, 72% (55 requests) were made to Sanoflore.fr and 7% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Sanoflore.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 361.0 kB (17%)

Content Size

2.1 MB

After Optimization

1.7 MB

In fact, the total size of Sanoflore.net main page is 2.1 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-9%

Potential reduce by 10 B

  • Original 108 B
  • After minification 108 B
  • After compression 98 B

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. This web page is already compressed.

Image Optimization

-2%

Potential reduce by 33.9 kB

  • Original 1.7 MB
  • After minification 1.6 MB

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. Sanoflore images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 173.8 kB

  • Original 250.2 kB
  • After minification 215.6 kB
  • After compression 76.3 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 173.8 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 153.2 kB

  • Original 177.1 kB
  • After minification 131.1 kB
  • After compression 23.9 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. Sanoflore.net needs all CSS files to be minified and compressed as it can save up to 153.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (41%)

Requests Now

66

After Optimization

39

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sanoflore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

sanoflore.net accessibility score

88

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

Links do not have a discernible name

Best Practices

sanoflore.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

sanoflore.net SEO score

87

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sanoflore.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 Sanoflore.net main page’s claimed encoding is . 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

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