smilesecret.de website review

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

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

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

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

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

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

4 third-party services load with your homepage (Shopify, shop.app and Heroku and others), adding 514 KiB and 168 ms of main-thread time.

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

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

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

1 image could be 39 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

4 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Month Ultimate Whitening Bundle”.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 103 ms to 121 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.0 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.0 MB in 245 requests on a phone: other files 809 KiB (113), scripts 539 KiB (99) and images 382 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example hf_20260605_094852_3af673a9-a69e-4a43-955a-d15d2bfbb9f6.jpg at 1,100 px wide, shown at 340 px. Resized copies would save about 8 KiB.

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

Certain ARIA roles must contain particular children: 5 elements on the page fail this check, rated critical by axe-core.

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

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

1 element hidden from screen readers can still receive keyboard focus.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is 71 characters, so Google will cut it off around 60: “Smile Secret® | Professionelle Zahnaufhellung für Zuhause – SmileSecret”.

There are 2 <h1> headlines (“BLACK MONTH DEALS” and “Sichtbar weißere Zähne — ohne Wasserstoffperoxid”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//smilesecret.de/cdn/shop/files/Logo-Smile-neu.png?v=17…”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 96 pages on smilesecret.de and 10 external pages.

Your homepage links to https://smilesecret.de/apps/17TRACK, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

https://smilesecret.de/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://smilesecret.de/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://smilesecret.de/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 422 ()”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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.

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

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