williamlambgroup.com website review

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

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

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

About 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 57 (desktop: 75). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Maps, Shopify and Yotpo and others), adding 1.2 MB and 270 ms of main-thread time.

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

10 KiB could be saved by minifying CSS.

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

Google Maps costs a phone 130 ms of main-thread work and 766 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.

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

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

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

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

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

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

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

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

5 images have no width and height attributes, so the layout jumps as each one loads.

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

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 4.0 MB in 307 requests on a phone: scripts 1.6 MB (68), images 1.0 MB (42) and other files 1.0 MB (173). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

The homepage links to 140 pages on williamlambgroup.com and 14 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://williamlambgroup.com/pages/get-in-touch, https://williamlambgroup.com/pages/faqs, https://williamlambgroup.com/pages/wishlist, https://williamlambgroup.com/collections/all-products, https://williamlambgroup.com/collections/boys and https://williamlambgroup.com/collections/clogs and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://williamlambgroup.com/collections/school and https://williamlambgroup.com/collections/school-1 use the same meta description. A description written for each page earns more clicks.

https://williamlambgroup.com/collections/new-in, https://williamlambgroup.com/collections/all-products, https://williamlambgroup.com/collections/boys, https://williamlambgroup.com/collections/school, https://williamlambgroup.com/collections/trainers and https://williamlambgroup.com/collections/sandals and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://williamlambgroup.com/.

14 of 68 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: the server responded with a status of 404 ()”.

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.

The homepage has only about 224 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 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 11 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.