waterdropfilter.de website review

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

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

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

8 third-party services load with your homepage (Shopify, consentmanager.net and xcottons.com and others), adding 2.1 MB and 951 ms of main-thread time.

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

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

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

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

consentmanager.net costs a phone 345 ms of main-thread work and 151 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.

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

xcottons.com costs a phone 93 ms of main-thread work and 324 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 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

2 KiB could be saved by minifying CSS.

Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bis zu 730 € Rabatt”.

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

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

Your homepage downloads 4.9 MB in 501 requests on a phone: scripts 2.4 MB (231), other files 938 KiB (180) and images 713 KiB (41). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.7 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 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: 4 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: 6 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 74 characters, so Google will cut it off around 60: “Hochwertige Umkehrosmoseanlage - Waterdrop Deutschland – Waterdrop Germany”.

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

The homepage links to 333 pages on waterdropfilter.de and 30 external pages.

https://www.waterdropfilter.de/collections/aufsatzfilter, https://www.waterdropfilter.de/collections/weitere-filter and https://www.waterdropfilter.de/collections/ro-ersatzfilter have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

https://www.waterdropfilter.de/pages/waterdrop-geschichte, https://www.waterdropfilter.de/products/g3p600-waterdrop-umkehrosmose-wasserfilteranlage, https://www.waterdropfilter.de/products/umkehrosmoseanlage-g3p800 and https://www.waterdropfilter.de/products/reverse-osmosis-system-waterdrop-x12 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.waterdropfilter.de/products/reverse-osmosis-system-waterdrop-x12 took over 3 s to send its HTML from our server.

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

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

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

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

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

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,392 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 Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (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 19 cookies (measured from a US location before any click).

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