savewater.co.uk website review

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

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

Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

17 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Facebook, Shopify and Google Tag Manager and others), adding 1.0 MB and 635 ms of main-thread time.

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

Facebook costs a phone 269 ms of main-thread work and 226 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 223 ms of main-thread work and 576 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 2,098 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

4 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' tap response (inp) went from 103 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.4 MB in 257 requests on a phone: media 13.0 MB (2), images 1.8 MB (40) and scripts 1.6 MB (112). Under 2 MB keeps phones on slow connections fast.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 133 pages on savewater.co.uk and 7 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://savewater.co.uk/customer_authentication/redirect and https://savewater.co.uk/cdn/shop/videos/c/vp/73ac9cd9344547bf9d4b5a373b740c7f/73ac9cd9344547bf9d4b5a373b740c7f.m3u8 have no <title>, so Google invents the link text in results.

https://savewater.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://savewater.co.uk/collections/frontpage/products/harcostar-350-litre-magnum-water-butt-triple-kit and https://savewater.co.uk/products/harcostar-350-litre-magnum-water-butt-triple-kit all use the title “Harcostar 350 Litre Magnum Water Butt – SaveWater.co.uk”. Search engines can't tell which page to show for a search, so each competes with the others.

https://savewater.co.uk/customer_authentication/redirect, https://savewater.co.uk/collections/all, https://savewater.co.uk/collections/water-butts, https://savewater.co.uk/collections/water-tanks, https://savewater.co.uk/collections/water-butt-accessories and https://savewater.co.uk/collections/garden and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://savewater.co.uk/collections/frontpage/products/harcostar-350-litre-magnum-water-butt-triple-kit and https://savewater.co.uk/products/harcostar-350-litre-magnum-water-butt-triple-kit use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://savewater.co.uk/collections/frontpage/products/harcostar-350-litre-magnum-water-butt-triple-kit, whose canonical is https://savewater.co.uk/products/harcostar-350-litre-magnum-water-butt-triple-kit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://savewater.co.uk/customer_authentication/redirect and https://savewater.co.uk/cdn/shop/videos/c/vp/73ac9cd9344547bf9d4b5a373b740c7f/73ac9cd9344547bf9d4b5a373b740c7f.m3u8 have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343248811&tm=gtm002&Ver=2&mid=ebdd0039-b492-4492-bf39-4b7fb8fa63fe&bo=1&sid=12a6bdf0dc8611f1a189d732b8e0d953&vid=12a6e2e0dc8611f1abdc050f57c76541&vids=1&msclkid=N&pi=9.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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 shows no opening hours. If customers visit or call, show when.

The homepage carries about 726 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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 20 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.