kleinkinderkram.de website review

Shopify costs a phone 2.0 s of main-thread work and 215 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.

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

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

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

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

8 third-party services load with your homepage (Shopify, iubenda and seguno.com and others), adding 585 KiB and 2.7 s of main-thread time.

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

iubenda costs a phone 552 ms of main-thread work and 125 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 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

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

Your homepage downloads 5.2 MB in 402 requests on a phone: images 3.3 MB (202), other files 946 KiB (142) and scripts 705 KiB (44). Under 2 MB keeps phones on slow connections fast.

BeBonnie-Logo_Zeichenflaeche_1_240x.png 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).

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your meta description is 289 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 430 pages on kleinkinderkram.de and 5 external pages.

https://bebonnie.de/collections/wichtelzubehor, https://bebonnie.de/collections/fur-mama, https://bebonnie.de/collections/fur-papa, https://bebonnie.de/collections/fur-oma, https://bebonnie.de/collections/fur-opa and https://bebonnie.de/collections/fur-uroma and 3 others use the same meta description. A description written for each page earns more clicks.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Social proof on the homepage: 28 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 1 more (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

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

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