fsah.fr website review

Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 1.0 MB and 493 ms of main-thread time.

About 298 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 239 ms of main-thread work and 353 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.5 s on main-thread work while loading, 888 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,730 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Klaviyo costs a phone 102 ms of main-thread work and 385 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

4 images could be 249 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

3 long tasks block the main thread while loading, the longest for 216 ms. During a long task the page ignores taps.

8 files are served with short cache lifetimes, so returning visitors download them again (114 KiB).

About 20 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

The page becomes fully interactive after 14.1 s. Good is under 3.8 s.

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.6 MB in 280 requests on a phone: images 1.3 MB (46), scripts 1.3 MB (83) and other files 841 KiB (134). Under 2 MB keeps phones on slow connections fast.

shopifymobile3.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example shopifymobile_2145991a-09c8-46ab-9317-d3ad616ef4c2_1220x.jpg at 1,220 px wide, shown at 350 px. Resized copies would save about 49 KiB.

1 image further down the page (188 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

8 tap targets are too small or too close together to hit reliably with a finger.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

The homepage links to 129 pages on fsah.fr and 11 external pages.

https://fsah.fr/apps/wpdapp, https://fsah.fr/collections/all, https://fsah.fr/collections/complement-alimentaire-pour-chevaux, https://fsah.fr/collections/consommables, https://fsah.fr/collections/purificateur-de-foin and https://fsah.fr/collections/equipement-decurie and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://fsah.fr/apps/wpdapp has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343127103&tm=gtm002&Ver=2&mid=4fa83df4-96c8-4833-8ce6-b85a0ad389a5&bo=1&sid=8ec2b6d0def311f19a4e1bfba1935029&vid=8ec2de40def311f1b0306d0781e95d99&vids=1&msclkid=N&gtm_.

18 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://settings.luckyorange.com/17e857bf' from origin 'https://fsah.fr' has been blocked by CORS p…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 747 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.