korres.fr website review

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

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

43 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

8 third-party services load with your homepage (monkcommerce.app, Klaviyo and Accessibe Accessibility Overlay and others), adding 1.7 MB and 585 ms of main-thread time.

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

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

monkcommerce.app costs a phone 112 ms of main-thread work and 544 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 107 ms of main-thread work and 309 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 95 ms of main-thread work and 407 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.

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

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

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

26 KiB JavaScript is shipped twice across bundles.

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Real visitors wait 208 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

The layout shifts by 0.186 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 7.3 MB in 414 requests on a phone: images 4.3 MB (78), scripts 1.6 MB (134) and other files 968 KiB (158). Under 2 MB keeps phones on slow connections fast.

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

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

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

Some list items are not inside a list.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

Your title is only 6 characters: “KORRES”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 173 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.

2 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 400 pages on korres.fr and 2 external pages.

https://www.korres.fr/collections/all-products and https://www.korres.fr/collections/tous-nos-produits all use the title “Découvrez tous nos produits – KORRES”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.korres.fr/collections/all-products and https://www.korres.fr/collections/tous-nos-produits use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.korres.fr/collections/all-products, whose canonical is https://www.korres.fr/collections/tous-nos-produits. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.korres.fr/collections/all-products, https://www.korres.fr/collections/super-rituels, https://www.korres.fr/collections/tous-nos-produits, https://www.korres.fr/collections/visage, https://www.korres.fr/collections/visage-yaourt-grec and https://www.korres.fr/collections/visage-pin-noir-primus have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.korres.fr/products/duo-smart-yoghurt-routinenuit, https://www.korres.fr/products/smart-yoghurt%E2%84%A2-creme-de-nuit-probiotiques-40ml, https://www.korres.fr/collections/tous-nos-produits, https://www.korres.fr/products/calendrier-de-lavent-2026, https://www.korres.fr/collections/visage and https://www.korres.fr/collections/visage-yaourt-grec and 1 other took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

4 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).

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

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