ponyhuetchen.com website review

38 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Reviews.io and Facebook and others), adding 2.6 MB and 2.7 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 930 ms faster on a phone.

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

Reviews.io costs a phone 350 ms of main-thread work and 376 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.

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

Facebook costs a phone 296 ms of main-thread work and 232 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.

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

admetrics.events costs a phone 283 ms of main-thread work and 84 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.

Klaviyo costs a phone 237 ms of main-thread work and 330 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 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.

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

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

8 KiB JavaScript is shipped twice across bundles.

6 KiB could be saved by minifying CSS.

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.

5 KiB could be saved by minifying JavaScript.

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

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PonyHütchen”.

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

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

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

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

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

Your homepage downloads 6.9 MB in 323 requests on a phone: scripts 3.2 MB (160), images 2.7 MB (27) and other files 642 KiB (98). Under 2 MB keeps phones on slow connections fast.

tannenzweige_ber_produkten_09341_Nano_Banana_Pro.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.95 g of CO₂e: 234.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

54 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

There are 6 <h1> headlines (“”, “Pony's Weihnachtsland” and “Der Rescue Balm”). One clear main headline is easier for people and search engines.

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

The homepage links to 171 pages on ponyhuetchen.com and 10 external pages.

There is no https://www.ponyhuetchen.com/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.ponyhuetchen.com/products/deocreme-mini-maxi and https://www.ponyhuetchen.com/products/deocremen-mini-maxi all use the title “Deocreme ohne Aluminium mit Natron | PonyHütchen”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ponyhuetchen.com/pages/shift-protect-allgemein and https://www.ponyhuetchen.com/pages/refillable-deostick have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ponyhuetchen.com/products/deocreme-mini-maxi and https://www.ponyhuetchen.com/products/deocremen-mini-maxi use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ponyhuetchen.com/products/deocremen-mini-maxi, whose canonical is https://www.ponyhuetchen.com/products/deocreme-mini-maxi. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ponyhuetchen.com/collections/deo-sets has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ponyhuetchen.com/pages/shift-protect-allgemein, https://www.ponyhuetchen.com/pages/refillable-deostick and https://www.ponyhuetchen.com/products/deocremen-mini-maxi took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 69 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=295005647&tm=gtm002&Ver=2&mid=f58c2c0c-c9af-4454-83bd-fab13495bec8&bo=1&sid=681541d0d9c511f19fe39df9dad07d38&vid=681568f0d9c511f19317339cd08534b9&vids=1&msclkid=N&pi=9.

6 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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