waterdropfilter.eu website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Amazon Web Services and consentmanager.net and others), adding 2.1 MB and 2.0 s of main-thread time.

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

Shopify costs a phone 527 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.

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

Amazon Web Services costs a phone 379 ms of main-thread work and 38 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 366 ms of main-thread work and 153 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 58 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

vanchat.app costs a phone 68 ms of main-thread work and 368 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 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.

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

11 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying CSS.

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

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

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

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

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

Your homepage downloads 5.7 MB in 545 requests on a phone: scripts 3.0 MB (268), images 999 KiB (50) and other files 882 KiB (177). Under 2 MB keeps phones on slow connections fast.

WD-M6-_Page_-_20260602V1__1_3.jpg 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 UK42-WD-10UA-__EWF-8016GK-UA-TB-UK_____20251125_V1-09-min.pn at 767 px wide, shown at 118 px. Resized copies would save about 43 KiB.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

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

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

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

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

The homepage links to 319 pages on waterdropfilter.eu and 17 external pages.

Your homepage links to https://www.waterdropfilter.eu/products/x16-undersink-reverse-osmosis-system and https://www.waterdropfilter.eu/products/reverse-osmosis-water-filtration-system-g3p600, which answer with an error. Visitors hit a dead end and search engines drop them.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 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>'”.

Chrome logged issues while loading the page (“Cookie”).

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 26 cookies, 2 of them by other companies (measured from a US location before any click).

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