happybrush.fr website review

14 images could be 729 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

8 third-party services load with your homepage (iubenda, frontapp.com and rise-ai.com and others), adding 2.1 MB and 818 ms of main-thread time.

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

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

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

frontapp.com costs a phone 333 ms of main-thread work and 1.5 MB 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.

iubenda costs a phone 393 ms of main-thread work and 125 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.

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

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

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

About 44 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.

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

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

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.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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

2 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 5.9 MB in 343 requests on a phone: images 1.8 MB (32), other files 1.3 MB (238) and scripts 1.3 MB (50). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example 1.Schall-Zahnbuerste-Eco.jpg at 2,679 px wide, shown at 50 px. Resized copies would save about 1.2 MB.

Hero_1_mobile.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).

4 images further down the page (442 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (82 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 105 pages on happybrush.fr and 10 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to https://happybrush.fr/pages/soin-dentaire, which answers with an error. Visitors hit a dead end and search engines drop it.

https://happybrush.fr/collections/singles-day, https://happybrush.fr/collections/brosses-a-dents, https://happybrush.fr/collections/junior, https://happybrush.fr/products/brosse-a-dents-sonique-eco-vibe-3, https://happybrush.fr/products/brosse-a-dents-sonique-eco-vibe-4 and https://happybrush.fr/products/brosse-dents-electrique-enfant-paw-patrol-set and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://happybrush.fr/collections/singles-day, https://happybrush.fr/collections/brosses-a-dents, https://happybrush.fr/collections/junior, https://happybrush.fr/products/brosse-a-dents-sonique-eco-vibe-3, https://happybrush.fr/products/brosse-a-dents-sonique-eco-vibe-4 and https://happybrush.fr/products/brosse-dents-electrique-enfant-paw-patrol-set and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://happybrush.fr/collections/junior, https://happybrush.fr/products/brosse-a-dents-sonique-eco-vibe-3 and https://happybrush.fr/products/brosse-a-dents-sonique-eco-vibe-4 took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “minMaxify is not defined”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 341 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 13 cookies (measured from a US location before any click).

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