thomann.de website review

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.6 s.

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

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

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

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

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

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

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

2 third-party services load with your homepage (Google Tag Manager and static-thomann.de), adding 1.2 MB and 88 ms of main-thread time.

static-thomann.de costs a phone 0 ms of main-thread work and 1.1 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.

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

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

11 KiB could be saved by minifying CSS.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mit unseren Cookies möchten wir Ihnen ein fluffiges Einkauf…”.

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

18 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 170 ms to 182 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.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 92 requests on a phone: images 1.1 MB (75), scripts 1.0 MB (5) and fonts 331 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example cyber-deals-oneliner.png at 1,920 px wide, shown at 220 px. Resized copies would save about 361 KiB.

3 images (483 KiB) 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.

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

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

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

36 images have no alt text, which hurts accessibility and image search.

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

15 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: 22 elements on the page fail this check, rated minor by axe-core.

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

Your title is 67 characters, so Google will cut it off around 60: “Musikinstrumente online kaufen beim Marktführer – Musikhaus Thomann”.

No XML sitemap at https://www.thomann.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 set, so this is minor.

The homepage links to 257 pages on thomann.de and 13 external pages.

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

robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.thomann.de/de/cat.html has no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

Large scripts ship without source maps.

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.

The homepage carries about 1,295 words of visible text.

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