nestera.fr website review

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

8 third-party services load with your homepage (YouTube, nestera.com and Google Tag Manager and others), adding 2.6 MB and 1.8 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page.

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

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

YouTube costs a phone 468 ms of main-thread work and 987 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.

nestera.com costs a phone 413 ms of main-thread work and 368 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.

Google Tag Manager costs a phone 357 ms of main-thread work and 468 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.

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

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

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

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

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

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

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

23 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

Real visitors wait 271 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' tap response (inp) went from 213 ms to 280 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 4.7 MB in 261 requests on a phone: scripts 2.7 MB (106), images 738 KiB (22) and other files 689 KiB (87). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 69 characters, so Google will cut it off around 60: “Nestera | Poulailler plastique facile à nettoyer | 25 ans de garantie”.

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("https:files/cover_facebook.png")”.

The homepage links to 114 pages on nestera.fr and 15 external pages.

/pages/help-center has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/help-center has no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://inflate-back.osc-fr1.scalingo.io/widgets/review.css?v=20260520a&color=%230a5e5e&st…”.

Chrome logged issues while loading the page (“Cookie”).

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.