nutritionpro.fr website review

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

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

Klaviyo costs a phone 274 ms of main-thread work and 511 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.7 s on main-thread work while loading, 805 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Klaviyo, loox.io and Shopify and others), adding 802 KiB and 454 ms of main-thread time.

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

3 images could be 28 KiB 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.

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

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

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

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

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

6 KiB could be saved by minifying CSS.

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.

3 KiB could be saved by minifying JavaScript.

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

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

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

5 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.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 210 requests on a phone: images 981 KiB (48), scripts 777 KiB (79) and other files 673 KiB (63). Under 2 MB keeps phones on slow connections fast.

Thes_infusions_du_monde.png 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).

3 images further down the page (87 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 0.75 g of CO₂e: 90.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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.

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

The homepage links to 314 pages on nutritionpro.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.

https://nutritionpro.fr/en/collections/all-slimming-products is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://nutritionpro.fr/en/pages/abonnement has no meta description, so Google writes the search snippet from whatever text it finds.

https://nutritionpro.fr/en/pages/abonnement has no <h1> headline, so visitors and search engines get no clear main topic.

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

11 of 44 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 “Cannot read properties of undefined (reading 'classList')”.

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 461 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, 2 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.