stier.de website review

209 images could be 26.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Google CDN and others), adding 1.1 MB and 635 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

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

Visually, the page fills in at 3.9 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 85 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 32.1 MB in 388 requests on a phone: images 29.7 MB (228), scripts 1,008 KiB (47) and other files 871 KiB (99). Under 2 MB keeps phones on slow connections fast.

39 images are downloaded at several times the size a phone draws them, for example stier-schaumstoff-schubladeneinlage-fuer-stier-werkstattwage at 2,000 px wide, shown at 280 px. Resized copies would save about 9.7 MB.

4 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

23 images further down the page (6.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images (1.5 MB) 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.

quickview line 22): invalid url input 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 9.11 g of CO₂e: 1092.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

149 tap targets are too small or too close together to hit reliably with a finger.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 920 pages on stier.de and 7 external pages.

There is no https://www.stier.de/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.

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

1 image failed to load on a phone, for example https://www.stier.de/Liquid%20error%20(snippets/quickview%20line%2022):%20invalid%20url%20input.

82 of 297 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 4,003 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 12 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.