lesdeux.com website review

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Cookie-Script.com and others), adding 2.7 MB and 1.5 s of main-thread time.

Shopify costs a phone 988 ms of main-thread work and 2.0 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 50. Pages that score under 90 lose visitors before the first paint.

About 595 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.

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

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

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

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

Klaviyo costs a phone 161 ms of main-thread work and 324 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 27 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 32 KiB JavaScript that modern phones do not need.

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 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

The first text or image appears after 3.2 s on a phone. Good is under 1.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 element shown below.

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

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

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 4.5 MB in 250 requests on a phone: images 2.5 MB (143), scripts 1.4 MB (55) and HTML 300 KiB (3). Under 2 MB keeps phones on slow connections fast.

5 images (200 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

23 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

2 dropdowns have no label.

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 9 elements on the page fail 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.

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

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

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

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

There are 10 <h1> headlines (“New in: Pre Spring ‘27”, “New Arrivals” and “Overshirts”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://lesdeux.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 110 pages on lesdeux.com and 11 external pages.

A phone browser shows 1,956 words, but the HTML your server sends has only 264. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

There is no https://lesdeux.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://lesdeux.com/collections/all and https://lesdeux.com/collections/clothing all use the title “Men’s Clothing | Les Deux”. Search engines can't tell which page to show for a search, so each competes with the others.

https://lesdeux.com/collections/coming-soon-ps27, https://lesdeux.com/collections/nfl and https://lesdeux.com/collections/clothing-como have no meta description, so Google writes the search snippet from whatever text it finds.

https://lesdeux.com/collections/all and https://lesdeux.com/collections/clothing use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://lesdeux.com/collections/all, whose canonical is https://lesdeux.com/collections/clothing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lesdeux.com/collections/sale took over 3 s to send its HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

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