simplehuman.co.uk website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Yotpo and iovation and others), adding 9.9 MB and 984 ms of main-thread time.

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

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

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

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

Google Tag Manager costs a phone 320 ms of main-thread work and 338 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.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Yotpo costs a phone 235 ms of main-thread work and 473 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.

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

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

Polyfills for old browsers add 56 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 116 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By using this site, you agree to the storing of cookies on …”.

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

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

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

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

The first text or image appears after 2.4 s on a phone. Good is under 1.8 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-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.7 MB in 275 requests on a phone: media 8.6 MB (1), scripts 1.4 MB (80) and other files 979 KiB (131). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example st3050-lifestyle_0d83680c-94e2-408e-8c38-220a02227607.jpg at 1,536 px wide, shown at 299 px. Resized copies would save about 85 KiB.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

The homepage links to 183 pages on simplehuman.co.uk and 41 external pages.

https://www.simplehuman.co.uk/collections/refills-liners, https://www.simplehuman.co.uk/collections/refills-soap and https://www.simplehuman.co.uk/collections/matte-black-shop are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.simplehuman.co.uk/pages/category-sensor-pump and https://www.simplehuman.co.uk/products/rechargeable-sensor-pump-9-fl-oz all use the title “Sensor Pump - Simplehuman”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.simplehuman.co.uk/pages/category-sensor-pump, https://www.simplehuman.co.uk/pages/category-sensor-mirror, https://www.simplehuman.co.uk/collections/refills-liners, https://www.simplehuman.co.uk/collections/refills-soap, https://www.simplehuman.co.uk/collections/matte-black-shop and https://www.simplehuman.co.uk/pages/category-sensor-can and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.simplehuman.co.uk/collections/all-trash, https://www.simplehuman.co.uk/collections/refills-liners, https://www.simplehuman.co.uk/collections/refills-soap and https://www.simplehuman.co.uk/collections/matte-black-shop have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 94 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 “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

The page uses urgency cues (a countdown or limited-time wording).

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