hofstrawagner.de website review

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 1.4 MB and 1.3 s of main-thread time.

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

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

About 641 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “KOSTENLOSER VERSAND AB €400”.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.2 MB in 232 requests on a phone: scripts 1.6 MB (79), images 743 KiB (18) and other files 687 KiB (93). Under 2 MB keeps phones on slow connections fast.

balu-sofa-havana-stof.webp 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.92 g of CO₂e: 110.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

[role="img"] and [role="image"] elements must have alternative text: 7 elements on the page fail this check, rated serious by axe-core.

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

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is 83 characters, so Google will cut it off around 60: “Ein Wohnuniversum für Möbel und Zubehör im skandinavischen Stil. – Hofstrawagner.de”.

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

Your <h1> is empty.

The homepage links to 108 pages on hofstrawagner.de and 8 external pages.

https://www.hofstrawagner.de/pages/schreiben-sie-uns, https://www.hofstrawagner.de/collections/neu, https://www.hofstrawagner.de/collections/runde-esstische, https://www.hofstrawagner.de/collections/stuhle, https://www.hofstrawagner.de/collections/esszimmerstuhle-in-velour and https://www.hofstrawagner.de/collections/esstischstuhle-aus-leder and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.hofstrawagner.de/pages/schreiben-sie-uns and https://www.hofstrawagner.de/collections have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Identifier 'highestNumber' has already been declared”.

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.

Social proof on the homepage: 23 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 864 words of visible text.

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

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

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