nu3.fr website review

14 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.6 s faster on a phone.

25 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).

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

About 348 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 950 ms faster on a phone.

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

7 third-party services load with your homepage (sa-tech.de, Usercentrics CMP and adtriba.com and others), adding 1.2 MB and 651 ms of main-thread time.

sa-tech.de costs a phone 543 ms of main-thread work and 969 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.

Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Promotion nu3”.

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Scripts block taps and scrolling for 388 ms in total while the page loads. Good is under 200 ms.

1 image 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' tap response (inp) went from 155 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.8 MB in 135 requests on a phone: images 4.1 MB (32), scripts 1.3 MB (67) and fonts 232 KiB (6). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example SAE_nu3-Produkte_Header-Image_nature_mobile_500x500px.png at 1,500 px wide, shown at 338 px. Resized copies would save about 1,003 KiB.

3 images (1.8 MB) 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.

SAE_nu3-Produkte_Header-Image_nature_mobile_500x500px.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).

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

There are 9 <h1> headlines (“nu3 chez Redcare. Profitez de votre avantage.”, “En exclusivité :” and “nu3 chez Redcare”). One clear main headline is easier for people and search engines.

The homepage links to 245 pages on nu3.fr and 15 external pages.

There is no https://www.redcare-pharmacie.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://www.redcare-pharmacie.fr/bons-plans, https://www.redcare-pharmacie.fr/offres-speciales and https://www.redcare-pharmacie.fr/nouveau are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.redcare-pharmacie.fr/nx/newsletter has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.redcare-pharmacie.fr/nx/newsletter, https://www.redcare-pharmacie.fr/offres-speciales and https://www.redcare-pharmacie.fr/nouveau have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.redcare-pharmacie.fr/offres-speciales and https://www.redcare-pharmacie.fr/nouveau took over 3 s to send their HTML from our server.

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

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

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

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

Opening the homepage sets 14 cookies (measured from a US location before any click).

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