sirplus.co.uk website review

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and Clarity and others), adding 1.6 MB and 1.0 s of main-thread time.

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

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

About 444 KiB of JavaScript is downloaded but never used on this page.

Klaviyo costs a phone 305 ms of main-thread work and 639 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.

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

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

9 long tasks block the main thread while loading, the longest for 103 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).

About 26 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

12 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Your homepage downloads 5.5 MB in 514 requests on a phone: images 1.9 MB (37), other files 1.5 MB (300) and scripts 1.4 MB (116). Under 2 MB keeps phones on slow connections fast.

Day2JamesRichardPhotographySirplusWinterCampaign-43_1244_bca 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).

1 image is downloaded at several times the size a phone draws it, for example Day2JamesRichardPhotographySirplusWinterCampaign-43_1244_bca at 1,250 px wide, shown at 390 px. Resized copies would save about 47 KiB.

1 image further down the page (46 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 247 pages on sirplus.co.uk and 11 external pages.

https://sirplus.co.uk/collections/all, https://sirplus.co.uk/collections/new-arrivals-autumn-winter-collection, https://sirplus.co.uk/pages/help-centre, https://sirplus.co.uk/collections/knitwear, https://sirplus.co.uk/collections/tweed-edit and https://sirplus.co.uk/collections/the-boiled-wool-edit and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sirplus.co.uk/collections/relaxed-tailoring and https://sirplus.co.uk/collections/accessories took over 3 s to send their HTML from our server.

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://bat.bing.net/action/0?ti=97078705&Ver=2&mid=1d0d34d1-102e-4b12-b307-8b561b45aff5&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=SIRPLUS%20%7C%20British%20menswear%20born%20from%20surp.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 mores (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 29 cookies, 1 of them by other companies (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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.