pelsbarn.de website review

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

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

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

5 images could be 82 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

1 long task block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.

8 third-party services load with your homepage (Cloudflare CDN, JSDelivr CDN and Shopify and others), adding 449 KiB and 5 ms of main-thread time.

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.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 164 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 2.6 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Evergreen_Q4_banner_-_Homepage_-_Mobile_4abeee77-d08b-40eb-b 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 0.37 g of CO₂e: 44.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 image has 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.

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 41 pages on pelsbarn.de and 5 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your robots.txt lets ChatGPT search (OAI-SearchBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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

https://pelsbarn.de/products/luxurioser-autositz-1-1-ip-5, https://pelsbarn.de/products/pelsbarn-kuhlendes-sofabett-4-mal-effektiver-bogo and https://pelsbarn.de/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://pelsbarn.de/collections/kollektion-26, https://pelsbarn.de/products/luxurioser-rucksitzschutz, https://pelsbarn.de/products/luxurioser-autositz-1-1-ip-5, https://pelsbarn.de/customer_authentication/redirect, https://pelsbarn.de/pages/faq and https://pelsbarn.de/collections/lux-collection and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pelsbarn.de/collections/kollektion-26, https://pelsbarn.de/pages/unsere-pelsbarn-mission, https://pelsbarn.de/customer_authentication/redirect, https://pelsbarn.de/apps/parcelpanel, https://pelsbarn.de/collections/lux-collection and https://pelsbarn.de/collections/original-car-bed and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://pelsbarn.de/apps/parcelpanel has 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.

https://pelsbarn.de/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://cdn.klaviyomail.com/company/XNJMPa/images/a791a225-4b3e-46d5-93b8-aaef4d6113a9.png.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID”.

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: 18 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 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, 1 of them by other companies (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 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.