etoile.com website review

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

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

8 third-party services load with your homepage (shopmy.us, Shopify and jQuery CDN and others), adding 11.7 MB and 77 ms of main-thread time.

Shopify costs a phone 19 ms of main-thread work and 11.6 MB 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.

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

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

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

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

26 KiB could be saved by minifying CSS.

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

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

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

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

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.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Free AU shipping on orders $200+”. Most of its time is element render delay (2.1 s).

Real visitors wait 233 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 25.2 MB in 763 requests on a phone: media 17.1 MB (5), images 6.9 MB (505) and other files 626 KiB (199). Under 2 MB keeps phones on slow connections fast.

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

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

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

1 dropdown has no label.

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

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

[role="img"] and [role="image"] elements must have alternative text: 5 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 78 characters, so Google will cut it off around 60: “The Best in Beauty Accessories, Makeup Storage, Makeup Bags & Mirrors - ETOILE”.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 255 pages on etoile.com and 1 external page.

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://etoile.com/collections/etoile-pro and https://etoile.com/pages/etoilepro all use the title “ETOILE PRO”. Search engines can't tell which page to show for a search, so each competes with the others.

https://etoile.com/collections/best-sellers, https://etoile.com/collections/toiletry-bags, https://etoile.com/collections/vanity-cases, https://etoile.com/collections/brushes, https://etoile.com/pages/build-your-set and https://etoile.com/pages/etoilepro and 1 other use the same meta description. A description written for each page earns more clicks.

https://etoile.com/collections/all, https://etoile.com/collections/best-sellers, https://etoile.com/collections/toiletry-bags, https://etoile.com/collections/beauty-cases, https://etoile.com/collections/vanity-cases and https://etoile.com/collections/capsule-case and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://etoile.com/collections/all, https://etoile.com/collections/best-sellers, https://etoile.com/collections/toiletry-bags, https://etoile.com/collections/beauty-cases, https://etoile.com/collections/vanity-cases and https://etoile.com/collections/capsule-case and 9 others have 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 28 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

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.

The homepage has only about 228 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Klaviyo (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 6 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.