wusthof.de website review

14 images could be 728 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

audioeye-services.com costs a phone 1.9 s of main-thread work and 302 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (audioeye-services.com, Google Tag Manager and Shopify and others), adding 2.5 MB and 3.4 s of main-thread time.

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

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

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

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

Shopify costs a phone 342 ms of main-thread work and 568 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.

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

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

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

51 KiB JavaScript is shipped twice across bundles.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

31 KiB could be saved by minifying JavaScript.

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

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.

2 KiB could be saved by minifying CSS.

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

Your largest element takes 8.3 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 7.4 s (Speed Index). Good is under 3.4 s.

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

5 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 109 ms to 125 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.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.1 MB in 360 requests on a phone: media 5.9 MB (2), scripts 2.5 MB (123) and images 1.4 MB (63). Under 2 MB keeps phones on slow connections fast.

wusthof_holiday_hero_mobile_2048x2048_f5c357d5-49a2-4bb4-8d4 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 3.16 g of CO₂e: 379.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

The homepage links to 186 pages on wusthof.de and 9 external pages.

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

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

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

https://wusthof.de/pages/holiday-gift-guide-2026, https://wusthof.de/pages/knife-finder, https://wusthof.de/pages/block-builder, https://wusthof.de/customer_authentication/redirect and https://wusthof.de/collections/bestseller have no meta description, so Google writes the search snippet from whatever text it finds.

https://wusthof.de/pages/knife-finder and https://wusthof.de/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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: 36 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Opening the homepage sets 21 cookies, 1 of them by other companies (measured from a US location before any click).

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