vax.co.uk website review

36 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

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

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

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

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

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

7 third-party services load with your homepage (Clarity, Optanon and Bazaarvoice and others), adding 679 KiB and 482 ms of main-thread time.

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

11 KiB JavaScript is shipped twice across bundles.

Desktop scores 84 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.

Polyfills for old browsers add 9 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.

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SAVE OVER £200 BLACK FRIDAY This year’s Black Friday has ar…”.

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

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

The layout shifts by 0.209 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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-24, real Chrome visitors' tap response (inp) went from 128 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

13 images are downloaded at several times the size a phone draws them, for example SPOTCLEANER.png at 1,024 px wide, shown at 188 px. Resized copies would save about 607 KiB.

Your homepage downloads 3.9 MB in 104 requests on a phone: images 2.8 MB (45), scripts 594 KiB (19) and fonts 198 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image (34 KiB) is 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.

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

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

Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.

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

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

Headings skip levels (h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 236 pages on vax.co.uk and 9 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.

/customer-services, /vacuum-cleaners/all-vacuum-cleaners, /vacuum-cleaners/long-reach-vacuums, /vacuum-cleaners/vacuums-with-toolkit and /vacuum-cleaners/all-vacuum-cleaners/liftout-upright-corded-vacuum-range 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 /vacuum-cleaners/corded-vacuum-cleaners/vax-liftout-multi-pet-upright-corded-vacuum-cleaner-with-toolkit, whose canonical is /vax-liftout-multi-pet-upright-corded-vacuum-cleaner-with-toolkit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/customer-services has no <h1> headline, so visitors and search engines get no clear main topic.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

vax.co.uk's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,936 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 18 cookies (measured from a US location before any click).

Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.