waterchef.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and alia-prod.com and others), adding 1.5 MB and 1.1 s of main-thread time.

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

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

Klaviyo costs a phone 261 ms of main-thread work and 500 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 283 ms of main-thread work and 279 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.

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

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

42 KiB could be saved by minifying JavaScript.

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

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

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

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.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.3 s. Good is under 3.8 s.

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

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

22 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 2.5 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 272 requests on a phone: scripts 1.7 MB (107), other files 765 KiB (113) and images 385 KiB (27). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

ARIA toggle fields do not have accessible names (2 elements).

1 link inside paragraphs relies on colour alone to stand out.

Some lists contain elements other than list items, which screen readers announce wrongly.

Structured data found (Corporation) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected token '/', ..."terChef", // Your Fa"... is not va)”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 121 pages on waterchef.com and 6 external pages.

Your homepage links to https://www.waterchef.com/collections/under-sink-countertop-filters, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.waterchef.com/products/waterchef-u9000-premium-under-sink-water-filtration-system and https://www.waterchef.com/collections/shop-products/products/waterchef-u9000-premium-under-sink-water-filtration-system all use the title “WaterChef U9000 Under-Sink Filter | IAPMO Certified”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.waterchef.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.waterchef.com/products/waterchef-u9000-premium-under-sink-water-filtration-system and https://www.waterchef.com/collections/shop-products/products/waterchef-u9000-premium-under-sink-water-filtration-system 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 https://www.waterchef.com/collections/shop-products/products/waterchef-u9000-premium-under-sink-water-filtration-system, whose canonical is https://www.waterchef.com/products/waterchef-u9000-premium-under-sink-water-filtration-system. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.waterchef.com/products/waterchef-u9000-premium-under-sink-water-filtration-system, https://www.waterchef.com/products/waterchef-sf-7c-premium-shower-filtration-system and https://www.waterchef.com/collections/shop-products/products/waterchef-u9000-premium-under-sink-water-filtration-system took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to fetch”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 47 words of visible text; thin pages give Google and first-time buyers little to go on.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, 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 6 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.