khadi.fr website review

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

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

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

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

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

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

8 third-party services load with your homepage (consentmanager.net, 506.io and Reviews.io and others), adding 534 KiB and 320 ms of main-thread time.

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

Polyfills for old browsers add 22 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.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your homepage downloads 5.2 MB in 269 requests on a phone: media 2.5 MB (1), scripts 872 KiB (85) and other files 865 KiB (129). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (8 elements).

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

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

The homepage links to 308 pages on khadi.fr and 10 external pages.

Your Organization JSON-LD is missing logo, 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.

There is no https://khadi.fr/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://khadi.fr/pages/color-quiz-khadi and https://khadi.fr/pages/rosemary-grow-croissance-capillaire have no meta description, so Google writes the search snippet from whatever text it finds.

https://khadi.fr/pages/color-quiz-khadi has no <h1> headline, so visitors and search engines get no clear main topic.

https://khadi.fr/collections/masques-ayurvediques-cheveux and https://khadi.fr/products/cheveux-wonder-hair-tonic took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d19ayerf5ehaab.cloudfront.net/css/product-widget/style.css' from origin 'https://k…”.

Large scripts ship without source maps.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,120 words of visible text.

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

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

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