nujime.com website review

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

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

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

About 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 440 ms faster on a phone.

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

Shopify costs a phone 245 ms of main-thread work and 543 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.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 924 KiB and 447 ms of main-thread time.

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

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

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

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

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

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

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

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

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

3 images are downloaded at several times the size a phone draws them, for example Melatonine_Flash_1_9mg_comprimes_Nujime_Laboratoires.webp at 200 px wide, shown at 60 px. Resized copies would save about 31 KiB.

6 images (299 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 0.48 g of CO₂e: 58.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

"role=text" should have no focusable descendants: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Your title is 91 characters, so Google will cut it off around 60: “BLACK FRIDAY ! -20% sur tout le site ! Nujimé | Laboratoires français – Nujimé Laboratoir…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 130 pages on nujime.com and 5 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://nujime.com/collections/complements-alimentaires-minceur, https://nujime.com/pages/programme-fidelite and https://nujime.com/pages/programme-abonnement have no meta description, so Google writes the search snippet from whatever text it finds.

https://nujime.com/pages/contact, https://nujime.com/pages/qui-sommes-nous, https://nujime.com/pages/programme-fidelite and https://nujime.com/pages/programme-abonnement have no <h1> headline, so visitors and search engines get no clear main topic.

https://nujime.com/collections/all, https://nujime.com/collections/complements-alimentaires-articulations, https://nujime.com/collections/complements-alimentaires-sante-sexuelle and https://nujime.com/collections/complements-alimentaires-beaute took over 3 s to send their HTML from our server.

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

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

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: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 15 fields (0 required). Every extra field lowers completion.

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

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