hoeffner.de website review

About 518 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

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

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

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

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

About 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

4 third-party services load with your homepage (Affiliate Window, ipdpx.de and Google Tag Manager and others), adding 18 KiB and 8 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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 527 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Warum auf Black Friday warten? Letzte Gelegenheit - nur bis…”.

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

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

For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.

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

12 images 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 265 ms to 271 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.8 MB in 163 requests on a phone: images 1.3 MB (66), scripts 1.2 MB (76) and fonts 81 KiB (5). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

15 buttons have no accessible name, so screen readers announce just “button”.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.hoeffner.de/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 847 pages on hoeffner.de and 2 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/moebel is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/warenkorb has no meta description, so Google writes the search snippet from whatever text it finds.

/standorte and /warenkorb have no <h1> headline, so visitors and search engines get no clear main topic.

/sofas, /2-sitzer, /3-sitzer and /wohnlandschaften took over 3 s to send their HTML from our server.

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

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

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

Large scripts ship without source maps.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

hoeffner.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,178 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads 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, 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.