stallplus.de website review

18 images could be 869 KiB 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.

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

8 third-party services load with your homepage (Shopify, PayPal and adcell.com and others), adding 1.5 MB and 847 ms of main-thread time.

Shopify costs a phone 551 ms of main-thread work and 967 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 466 KiB of JavaScript is downloaded but never used on this page.

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

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

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

PayPal costs a phone 207 ms of main-thread work and 387 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.

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

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

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

58 KiB JavaScript is shipped twice across bundles.

About 25 KiB of CSS is downloaded but never applied on this page.

6 KiB could be saved by minifying CSS.

6 KiB could be saved by minifying JavaScript.

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 16.9 s. Good is under 3.8 s.

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

Visually, the page fills in at 4.5 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 90 ms to 95 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.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.7 MB in 393 requests on a phone: images 1.8 MB (39), scripts 1.3 MB (158) and other files 864 KiB (143). Under 2 MB keeps phones on slow connections fast.

1000047137_Produktverschonerer_-Photoroom.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).

1 image is downloaded at several times the size a phone draws it, for example 20260629_103054.jpg at 326 px wide, shown at 60 px. Resized copies would save about 47 KiB.

1 image further down the page (28 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 1.33 g of CO₂e: 159.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Links must have discernible text: 5 elements on the page fail 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.

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

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

Your <h1> is empty.

The homepage links to 224 pages on stallplus.de and 3 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.

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

https://stallplus.de/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://stallplus.de/customer_authentication/redirect and https://stallplus.de/collections/mobile-huhnerstalle-bis-18-huhner have no meta description, so Google writes the search snippet from whatever text it finds.

https://stallplus.de/collections/huhnerstall-fur-8-huhner/H%C3%BChnerst%C3%A4lle-f%C3%BCr-8-H%C3%BChner and https://stallplus.de/collections/huhnerstall-fur-8-huhner-2-radig/H%C3%BChnerstall-f%C3%BCr-8-H%C3%BChner-2r%C3%A4dig use the same meta description. A description written for each page earns more clicks.

Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://stallplus.de/collections/huhnerstall-fur-6-huhner/H%C3%BChnerst%C3%A4lle-6-H%C3%BChner, whose canonical is https://stallplus.de/collections/huhnerstall-fur-6-huhner. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://stallplus.de/customer_authentication/redirect, https://stallplus.de/collections/mobile-huhnerstalle-bis-18-huhner, https://stallplus.de/collections/huhnerstall-fur-6-huhner/H%C3%BChnerst%C3%A4lle-6-H%C3%BChner, https://stallplus.de/collections/huhnerstall-fur-6-huhner-mit-4-fusse/H%C3%BChnerstall-f%C3%BCr-6-H%C3%BChner-mit-4-F%C3%BC%C3%9Fe, https://stallplus.de/collections/huhnerstall-fur-6-huhner-mit-2-rader/H%C3%BChnerstall-f%C3%BCr-6-H%C3%BChner-mit-2-R%C3%A4der and https://stallplus.de/collections/huhnerstall-fur-6-huhner-mit-4-rader/H%C3%BChnerstall-f%C3%BCr-6-H%C3%BChner-mit-4-R%C3%A4der and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://stallplus.de/collections/huhnerstall-fur-6-huhner-mit-2-rader/H%C3%BChnerstall-f%C3%BCr-6-H%C3%BChner-mit-2-R%C3%A4der, https://stallplus.de/collections/huhnerstall-fur-6-huhner-mit-4-rader/H%C3%BChnerstall-f%C3%BCr-6-H%C3%BChner-mit-4-R%C3%A4der, https://stallplus.de/collections/huhnerstall-fur-8-huhner/H%C3%BChnerst%C3%A4lle-f%C3%BCr-8-H%C3%BChner, https://stallplus.de/collections/huhnerstalle-fur-bis-zu-8-huhner-mit-4-fusse/8-H%C3%BChner-mit-4-F%C3%BC%C3%9Fe, https://stallplus.de/collections/huhnerstall-fur-8-huhner-2-radig/H%C3%BChnerstall-f%C3%BCr-8-H%C3%BChner-2r%C3%A4dig and https://stallplus.de/collections/huhnerstall-fur-8-huhner-4-rader/H%C3%BChnerstall-f%C3%BCr-8-H%C3%BChner-mit-4-R%C3%A4der-Allrad and 3 others took over 3 s to send their HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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

Social proof on the homepage: 13 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.

The homepage shows no opening hours. If customers visit or call, show when.

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

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