smileunion.de website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Trust Pilot and others), adding 6.9 MB and 200 ms of main-thread time.

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

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

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

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

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

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Gerade Zähne vom Testsieger schon ab 30€ pro Monat. Starte …”.

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

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

19 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 112 ms to 122 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.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.7 MB in 202 requests on a phone: media 6.3 MB (3), other files 830 KiB (112) and scripts 750 KiB (44). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example ntv-Testsieger-2026.png at 3,703 px wide, shown at 267 px. Resized copies would save about 89 KiB.

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

9 text elements don'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.

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

Your title is 66 characters, so Google will cut it off around 60: “Unsichtbare Zahnkorrektur vom Testsieger - schon ab 30€ pro Monat!”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 25 pages on smileunion.de and 6 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.smileunion.de/pages/wie-funktioniert-s, https://www.smileunion.de/pages/pricing, https://www.smileunion.de/pages/anleitung, https://www.smileunion.de/pages/vor-ort-termine, https://www.smileunion.de/pages/erfahrungen and https://www.smileunion.de/blogs/wissenswertes have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.smileunion.de/blogs/wissenswertes has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.smileunion.de/pages/kontakt and https://www.smileunion.de/pages/impressum have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'protect' of object '#<Object>'”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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

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