ledbury.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Accessibe Accessibility Overlay and others), adding 990 KiB and 699 ms of main-thread time.

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

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

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

Google Tag Manager costs a phone 273 ms of main-thread work and 187 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.

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

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

About 44 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.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A man wearing a gray windowpane plaid blazer over a light g…”.

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

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

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

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

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

Your homepage downloads 4.0 MB in 204 requests on a phone: images 1.7 MB (32), scripts 1.2 MB (68) and other files 738 KiB (84). Under 2 MB keeps phones on slow connections fast.

5W22T9-206-1-The-Apricot-Hartmann-Flannel-lifestyle-1.webp 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).

7 images (630 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.

4 images are downloaded at several times the size a phone draws them, for example 5W22T9-805-1-The-Soft-Brown-Hartmann-Flannel2-lifestyle_1_op at 600 px wide, shown at 147 px. Resized copies would save about 134 KiB.

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

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

All page content should be contained by landmarks: 13 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.

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

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

Your <h1> is empty.

The homepage links to 121 pages on ledbury.com and 4 external pages.

https://www.ledbury.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.ledbury.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.ledbury.com/pages/customer-reviews, https://www.ledbury.com/pages/fit-guide, https://www.ledbury.com/collections/sweaters, https://www.ledbury.com/collections/sale, https://www.ledbury.com/customer_authentication/redirect and https://www.ledbury.com/collections/white-shirts and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ledbury.com/pages/60-day-guarantee, https://www.ledbury.com/pages/fit-guide, https://www.ledbury.com/collections/all-shirts, https://www.ledbury.com/collections/sweaters, https://www.ledbury.com/collections/all-clothing and https://www.ledbury.com/collections/sale and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ledbury.com/collections/all-shirts, https://www.ledbury.com/collections/sweaters, https://www.ledbury.com/collections/all-clothing, https://www.ledbury.com/collections/white-shirts, https://www.ledbury.com/collections/non-iron-dress-shirts and https://www.ledbury.com/collections/pants and 4 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 errors were logged to the browser console while the page loaded, for example “await is only valid in async functions and the top level bodies of modules”.

The homepage carries about 542 words of visible text.

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