zahnheld.de website review

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Shopify, Klaviyo and Facebook and others), adding 2.4 MB and 1.4 s of main-thread time.

About 660 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

Klaviyo costs a phone 299 ms of main-thread work and 624 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.

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

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

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

smile.io costs a phone 88 ms of main-thread work and 460 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.

7 images could be 220 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

44 KiB could be saved by minifying JavaScript.

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

17 KiB JavaScript is shipped twice across bundles.

6 KiB could be saved by minifying CSS.

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.

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 22.6 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.8 s (Speed Index). Good is under 3.4 s.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 174 ms to 205 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 14.6 MB in 524 requests on a phone: media 9.3 MB (4), scripts 2.5 MB (257) and other files 1,001 KiB (186). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (140 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

4 form fields have 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.

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

Your title is 67 characters, so Google will cut it off around 60: “Zahnheld® | Elektrische Schallzahnbürsten, Munddusche und Zahnpasta”.

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

The homepage links to 114 pages on zahnheld.de and 12 external pages.

https://zahnheld.de/blogs/zahnheld-blog has no meta description, so Google writes the search snippet from whatever text it finds.

https://zahnheld.de/pages/kontakt has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 1 more (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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.