lillyparis.fr website review

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

About 142 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Clarity, Snapchat and cloudfront.net and others), adding 406 KiB and 296 ms of main-thread time.

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

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

4 KiB could be saved by minifying CSS.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.8 MB in 201 requests on a phone: images 1.2 MB (30), other files 786 KiB (94) and scripts 564 KiB (55). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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: 1 element on the page fails this check, rated moderate by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 80 characters, so Google will cut it off around 60: “N°1 du Démaquillage Zéro-Déchet - Le Pad le plus durable du monde ! – Lilly Skin”.

Your canonical URL points to lilly-skin.com, not lillyparis.fr, so Google may credit that host instead.

Structured data found (FAQPage, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://lilly-skin.com)”.

The homepage links to 124 pages on lillyparis.fr and 5 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://lillyparis.fr/products/taie-oreiller is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://lillyparis.fr/products/taie-oreiller and https://lillyparis.fr/collections/pillowcase all use the title “Taie d'oreiller – Lilly Skin”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://lillyparis.fr/collections/all, https://lillyparis.fr/collections/masques, https://lillyparis.fr/collections/cheveux, https://lillyparis.fr/collections/coffrets, https://lillyparis.fr/collections/destockage and https://lillyparis.fr/pages/lilly-tout-savoir-sur-soie and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://lillyparis.fr/collections/all, https://lillyparis.fr/collections/pillowcase, https://lillyparis.fr/collections/masque-3d-classique-new-website, https://lillyparis.fr/collections/chouchou-en-soie, https://lillyparis.fr/collections/bonnet-en-soie and https://lillyparis.fr/collections/kit-boucles-sans-chaleur have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

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