safelit.fr website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

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

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

8 third-party services load with your homepage (ContentSquare, Clarity and Klaviyo and others), adding 1.2 MB and 1.0 s of main-thread time.

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

About 336 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

ContentSquare costs a phone 483 ms of main-thread work and 185 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.

Klaviyo costs a phone 170 ms of main-thread work and 313 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.

Shopify costs a phone 68 ms of main-thread work and 396 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

About 30 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

11 KiB JavaScript is shipped twice across bundles.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Visually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 149 ms to 174 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Piqûres au réveil, traces suspectes, démangeaisons ? Avant …”. Most of its time is element render delay (2.5 s).

Scripts block taps and scrolling for 310 ms in total while the page loads. Good is under 200 ms.

Your homepage downloads 3.5 MB in 234 requests on a phone: images 1.2 MB (22), scripts 1.0 MB (74) and other files 1.0 MB (120). Under 2 MB keeps phones on slow connections fast.

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

3 images have no alt text, which hurts accessibility and image search.

1 button has no accessible name, so screen readers announce just “button”.

11 visible links have no text or label, so screen readers cannot say where they go.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Your title is 67 characters, so Google will cut it off around 60: “Traitement Punaise de Lit, Housse, fumigène & Insecticide - SAFELIT”.

Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 105 pages on safelit.fr and 6 external pages.

A phone browser shows 4,280 words, but the HTML your server sends has only 1,118. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

https://safelit.fr/pages/diagnostic-gratuit has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 4,280 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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 20 cookies (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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.