thelingerist.com website review

344 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

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

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

Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

20 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

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

5 third-party services load with your homepage (Klaviyo, Trust Pilot and digitaloceanspaces.com and others), adding 1.0 MB and 201 ms of main-thread time.

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

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

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

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

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

Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (6.1 s).

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

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

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

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 5.0 MB in 391 requests on a phone: images 2.5 MB (304), scripts 1.2 MB (43) and other files 1.0 MB (35). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

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

Your title is only 13 characters: “The Lingerist”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/Untitled_design_14.png")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 234 pages on thelingerist.com and 5 external pages.

There is no https://thelingerist.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://thelingerist.com/collections/bras-1, https://thelingerist.com/collections/wireless-bras, https://thelingerist.com/collections/underwire-bras, https://thelingerist.com/collections/padded-bras, https://thelingerist.com/collections/unpadded-bras and https://thelingerist.com/collections/longline-bras and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

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 1 cookie (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.