nuclever.fr website review

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

10 images could be 206 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

5 third-party services load with your homepage (Google Tag Manager, Shopify and Google Fonts and others), adding 1.5 MB and 44 ms of main-thread time.

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

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

replocdn.com costs a phone 0 ms of main-thread work and 693 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.

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

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

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

25 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.

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nutritional supplement packet with pink drink and mixer, al…”.

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

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

9 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 247 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1_Packshot_1_cdf6be06-2878-42b9-9f82-49e9f2defcd1.webp weighs 491 KiB. On a phone connection a single image that size takes seconds.

1_Packshot_1_cdf6be06-2878-42b9-9f82-49e9f2defcd1.webp 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 (598 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.

1 image further down the page (49 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

There are 2 <h1> headlines (“” and “Comment Utiliser”). One clear main headline is easier for people and search engines.

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

The homepage links to 94 pages on nuclever.fr and 1 external page.

https://nuclever.fr/pages/nuclever is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://nuclever.fr/pages/nuclever all use the title “Nuclever Cortisol Manager – Nuclever France”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nuclever.fr/pages/homme and https://nuclever.fr/pages/blog have no meta description, so Google writes the search snippet from whatever text it finds.

https://nuclever.fr/pages/nuclever, https://nuclever.fr/pages/homme, https://nuclever.fr/products/enzymes-digestives-manager, https://nuclever.fr/products/appetit-manager and https://nuclever.fr/products/dht-manager have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Social proof on the homepage: a star rating. 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,344 words of visible text.

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