liliclaspe.com website review

8 third-party services load with your homepage (Shopify, Clarity and Accessibe Accessibility Overlay and others), adding 2.1 MB and 822 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

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

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

2 KiB could be saved by minifying CSS.

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

The layout shifts by 0.574 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Visually, the page fills in at 5.0 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.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 112 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 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.7 MB in 330 requests on a phone: media 11.8 MB (5), scripts 2.1 MB (116) and images 1.1 MB (29). Under 2 MB keeps phones on slow connections fast.

Fall26_Homepage_Full_Mobile_1_3a4e71b0-0128-47b1-99b8-99c469 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 4.73 g of CO₂e: 567.3 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.

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

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

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 11 characters: “Lili Claspe”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 9 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 82 pages on liliclaspe.com and 15 external pages.

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://www.liliclaspe.com/collections/shop-all, https://www.liliclaspe.com/collections/new-arrivals, https://www.liliclaspe.com/collections/necklaces, https://www.liliclaspe.com/collections/tennis, https://www.liliclaspe.com/collections/earrings and https://www.liliclaspe.com/collections/rings and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.liliclaspe.com/collections/shop-all, https://www.liliclaspe.com/collections/new-arrivals, https://www.liliclaspe.com/collections/necklaces, https://www.liliclaspe.com/collections/earrings, https://www.liliclaspe.com/collections/bracelets and https://www.liliclaspe.com/collections/bridal-edit and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

15 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 “Failed to load resource: net::ERR_FAILED”.

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

The page uses urgency cues (a countdown or limited-time wording).

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