naturecos.com website review

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

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

8 third-party services load with your homepage (Shopify, roseperl.com and Google Tag Manager and others), adding 1.3 MB and 1.3 s of main-thread time.

30 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

roseperl.com costs a phone 258 ms of main-thread work and 431 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.

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

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

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

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

51 KiB JavaScript is shipped twice across bundles.

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

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

10 KiB could be saved by minifying CSS.

8 KiB could be saved by minifying JavaScript.

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 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image mobile banner 1”.

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

The page becomes fully interactive after 23.2 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 121 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

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

Your homepage downloads 5.0 MB in 326 requests on a phone: images 2.0 MB (60), scripts 1.3 MB (97) and other files 1.2 MB (119). Under 2 MB keeps phones on slow connections fast.

13 images are downloaded at several times the size a phone draws them, for example 342f237f-6f20-49c6-acf0-a87371678bc1.png at 2,208 px wide, shown at 350 px. Resized copies would save about 604 KiB.

23 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

11 images (1.3 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.

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

3 buttons have no accessible name, so screen readers announce just “button”.

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

1 image has 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 70 characters, so Google will cut it off around 60: “Naturecos - Cosmétiques bio | Couleur Caramel, Miss W Pro – Nature COS”.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("Liquid error (snippets/schema line 28): invalid url inp…”.

The homepage links to 188 pages on naturecos.com and 7 external pages.

https://www.naturecos.com/collections/teint-nc/Couleur-Caramel, https://www.naturecos.com/collections/yeux-nc/Couleur-Caramel, https://www.naturecos.com/collections/levres-nc/Couleur-Caramel, https://www.naturecos.com/collections/mains-ongles-nc/Couleur-Caramel, https://www.naturecos.com/collections/pinceaux-couleur-caramel/Couleur-Caramel and https://www.naturecos.com/collections/teint-nc/Miss-W-Pro and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.naturecos.com/collections/teint-nc/Couleur-Caramel and https://www.naturecos.com/collections/teint-nc/Miss-W-Pro all use the title “Teint NC bio | Nature COS”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.naturecos.com/collections/teint-nc/Couleur-Caramel and https://www.naturecos.com/collections/teint-nc/Miss-W-Pro use the same meta description. A description written for each page earns more clicks.

https://www.naturecos.com/pages/wish-list, https://www.naturecos.com/collections/teint-nc/Couleur-Caramel, https://www.naturecos.com/collections/yeux-nc/Couleur-Caramel, https://www.naturecos.com/collections/levres-nc/Couleur-Caramel, https://www.naturecos.com/collections/mains-ongles-nc/Couleur-Caramel and https://www.naturecos.com/collections/pinceaux-couleur-caramel/Couleur-Caramel and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.naturecos.com/pages/wish-list has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

3 errors were logged to the browser console while the page loaded, for example “Identifier 'searchModal' has already been declared”.

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

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