lysse.com website review

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

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

8 third-party services load with your homepage (Klaviyo, Yotpo and Accessibe Accessibility Overlay and others), adding 2.4 MB and 885 ms of main-thread time.

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

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

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

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

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

Shopify costs a phone 71 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.

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

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

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

64 KiB could be saved by minifying JavaScript.

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

23 KiB could be saved by minifying CSS.

11 KiB JavaScript is shipped twice across bundles.

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.

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 737 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

Real visitors wait 820 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 306 ms to 302 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.3 MB in 510 requests on a phone: images 3.3 MB (271), scripts 1.7 MB (93) and other files 804 KiB (116). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.1 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: 68 elements on the page fail this check, rated serious by axe-core.

2 images have 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.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

Your title is 72 characters, so Google will cut it off around 60: “Lyssé New York | Urban-inspired, comfort-focused women's fashion – LYSSÉ”.

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

The homepage links to 285 pages on lysse.com and 3 external pages.

https://www.lysse.com/pages/rewards has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lysse.com/collections/lysse-fit, https://www.lysse.com/collections/all-new, https://www.lysse.com/collections/new-tops-1, https://www.lysse.com/collections/new-jackets, https://www.lysse.com/collections/new-bottoms and https://www.lysse.com/collections/new-denim-1 and 7 others use the same meta description. A description written for each page earns more clicks.

https://www.lysse.com/collections/lysse-fit, https://www.lysse.com/pages/rewards, https://www.lysse.com/collections/all-new, https://www.lysse.com/collections/new-tops-1, https://www.lysse.com/collections/new-jackets and https://www.lysse.com/collections/new-bottoms and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.slpht.com/widget/stylesheets/slpht_d46b6d5c37697a9435ff484c42e1460f.css' from …”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 233 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 Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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 24 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.