lisettel.com website review

20 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Clarity and roseperl.com and others), adding 2.5 MB and 332 ms of main-thread time.

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

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

Klaviyo costs a phone 144 ms of main-thread work and 309 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.

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

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

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 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lisette L Holiday Edit: new arrivals for the holidays”.

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

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

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

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

Your homepage downloads 3.8 MB in 232 requests on a phone: images 1.9 MB (26), scripts 895 KiB (74) and other files 673 KiB (78). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (939 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

8 images are downloaded at several times the size a phone draws them, for example Tigers_Eyee_1616_pocket.png at 1,122 px wide, shown at 320 px. Resized copies would save about 372 KiB.

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

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

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

There are 4 <h1> headlines (“Lisette L Montreal - USA”, “Lightweight Jolie Crepe 25" Athens Wide Crop” and “Better Together: Lisette L × Trisha Tyler”). One clear main headline is easier for people and search engines.

Your meta description is 256 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 94 pages on lisettel.com and 4 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://lisettel.com/collections/new-arrivals, https://lisettel.com/collections/dresses, https://lisettel.com/collections/reversibles, https://lisettel.com/collections/outerwear, https://lisettel.com/collections/sale-collection and https://lisettel.com/collections/new-arrivals-jackets and 3 others use the same meta description. A description written for each page earns more clicks.

https://lisettel.com/collections/new-arrivals and https://lisettel.com/collections/basics have no <h1> headline, so visitors and search engines get no clear main topic.

https://lisettel.com/collections/pants, https://lisettel.com/collections/tops and https://lisettel.com/collections/basics took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Identifier 'checkVersion' has already been declared”.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 608 words of visible text.

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