waterdropfilter.com website review

Amazon Web Services costs a phone 1.4 s of main-thread work and 30 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 13.8 s on main-thread work while loading, 7.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (Amazon Web Services, consentmanager.net and Google Tag Manager and others), adding 2.7 MB and 4.1 s of main-thread time.

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

54 files are served with short cache lifetimes, so returning visitors download them again (1,013 KiB).

Google Tag Manager costs a phone 658 ms of main-thread work and 539 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.

consentmanager.net costs a phone 692 ms of main-thread work and 158 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 529 ms of main-thread work and 1.1 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.

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

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

10 images could be 269 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Sentry costs a phone 253 ms of main-thread work and 48 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.

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

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

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

Your largest element takes 7.6 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 12.0 s (Speed Index). Good is under 3.4 s.

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

3 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 6.6 MB in 638 requests on a phone: scripts 3.7 MB (275), other files 1.1 MB (252) and images 946 KiB (53). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example wd-product-a2g-design-img-1.webp at 359 px wide, shown at 118 px. Resized copies would save about 2 KiB.

3 images (211 KiB) are 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.87 g of CO₂e: 224.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

ARIA role should be appropriate for the element: 13 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 66 characters, so Google will cut it off around 60: “Reverse Osmosis Water Filters & Water Purifier Systems | Waterdrop”.

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

The homepage links to 521 pages on waterdropfilter.com and 34 external pages.

https://www.waterdropfilter.com/collections/undersink-ro-systems, https://www.waterdropfilter.com/collections/undersink-ro-systems/waterdrop-x-series, https://www.waterdropfilter.com/collections/undersink-ro-systems/waterdrop-g-series and https://www.waterdropfilter.com/collections/undersink-ro-systems/waterdrop-k-series use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.waterdropfilter.com/collections/undersink-ro-systems/waterdrop-x-series, whose canonical is https://www.waterdropfilter.com/collections/undersink-ro-systems. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.waterdropfilter.com/collections/reverse-osmosis-water-filter-all, https://www.waterdropfilter.com/collections/waterdrop-undersink-water-filtration-system, https://www.waterdropfilter.com/collections/countertop-water-filters, https://www.waterdropfilter.com/collections/whole-house-water-filters, https://www.waterdropfilter.com/pages/reverse-osmosis-water-system-xseries and https://www.waterdropfilter.com/products/ro-system-for-home-alkaline-x8-a took over 3 s to send their HTML from our server.

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

24 of 120 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

1 image is served at too low a resolution for sharp phone screens.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,012 words of visible text.

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

Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 5 mores (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

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

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