kleinewolke.com website review

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

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

31 images could be 1.1 MB 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.

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

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

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

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

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

Klaviyo costs a phone 248 ms of main-thread work and 312 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.

Clarity costs a phone 269 ms of main-thread work and 29 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 82 ms of main-thread work and 725 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.

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Modernes Bad mit freistehender Wanne und farbigen Badematte…”.

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

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

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

Your homepage downloads 4.8 MB in 423 requests on a phone: images 1.8 MB (82), scripts 1.6 MB (167) and other files 1.0 MB (120). Under 2 MB keeps phones on slow connections fast.

kleine-wolke-bt-relax-startseite-mehr-kachel-261x261.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).

4 images are downloaded at several times the size a phone draws them, for example kleine-wolke-badteppich-relax-anthrazit-60-x-100-cm-54059013 at 450 px wide, shown at 57 px. Resized copies would save about 362 KiB.

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

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

33 visible links have no text or label, so screen readers cannot say where they go.

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

Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h4 → h6), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (5 elements).

The homepage links to 608 pages on kleinewolke.com and 0 external pages.

https://www.kleinewolke.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.kleinewolke.com/pages/wunschliste and https://www.kleinewolke.com/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.kleinewolke.com/pages/wunschliste and https://www.kleinewolke.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kleinewolke.com/pages/wunschliste, https://www.kleinewolke.com/customer_authentication/redirect, https://www.kleinewolke.com/collections/badteppiche-unifarben, https://www.kleinewolke.com/collections/badteppiche-gemustert, https://www.kleinewolke.com/collections/badteppiche-motiv and https://www.kleinewolke.com/collections/frottier-vorleger and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kleinewolke.com/collections/badteppiche-unifarben, https://www.kleinewolke.com/collections/badteppiche-gemustert, https://www.kleinewolke.com/collections/badteppiche-motiv, https://www.kleinewolke.com/collections/wc-vorleger, https://www.kleinewolke.com/collections/wc-deckelbezuege and https://www.kleinewolke.com/collections/duschrollos and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

Large scripts ship without source maps.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Klaviyo, Microsoft Ads and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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