waschbaer.de website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, trbo.com and consentmanager.net and others), adding 1.5 MB and 1.8 s of main-thread time.

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

19 images could be 1,023 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

trbo.com costs a phone 333 ms of main-thread work and 248 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 312 ms of main-thread work and 135 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 108 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.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.60 (75th percentile). Good is under 0.1.

Your largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bekleidung.”.

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

The layout shifts by 0.662 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 861 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 122 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.5 MB in 219 requests on a phone: images 9.6 MB (112), scripts 1.6 MB (49) and fonts 162 KiB (5). Under 2 MB keeps phones on slow connections fast.

8 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.

16 images (7.3 MB) 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.

1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

26 elements hidden from screen readers can still receive keyboard focus.

5 tap targets are too small or too close together to hit reliably with a finger.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Headings skip levels (h2 → h5 and h1 → h3), which makes the page harder to scan with a screen reader.

Your title is only 28 characters: “Waschbär – Der Umweltversand”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Nachhaltige Produkte für einen bewussten Alltag” and “Herzlich willkommen im Onlineshop vom Waschbär.”). One clear main headline is easier for people and search engines.

Structured data found (Organization and SiteNavigationElement) but with 2 problems, for example “Organization: missing name”.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 200 pages on waschbaer.de and 4 external pages.

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

There is no https://www.waschbaer.de/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.waschbaer.de/kontakt, https://www.waschbaer.de/newsletter and https://www.waschbaer.de/warenkorb are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://www.waschbaer.de/startseite all use the title “Waschbär – Der Umweltversand”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.waschbaer.de/online-katalog, https://www.waschbaer.de/kontakt, https://www.waschbaer.de/online-bestellschein, https://www.waschbaer.de/newsletter, https://www.waschbaer.de/warenkorb and https://www.waschbaer.de/geschenk-gutscheine and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.waschbaer.de/kontakt, https://www.waschbaer.de/online-bestellschein and https://www.waschbaer.de/warenkorb have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 75 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=134595907&tm=gtm002&Ver=2&mid=c5a63951-d0ca-483e-a788-abe2a07e9e5f&bo=8&sid=9d76ac80cbf011f1af21c938b1c9deb0&vid=9d7706e0cbf011f19e21d55255dba700&vids=0&msclkid=N&pi=9.

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

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.

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,210 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 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 16 cookies (measured from a US location before any click).

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