schulte.de website review

100 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

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

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

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

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

4 third-party services load with your homepage (Amazon Web Services, Trust Pilot and Other Google APIs/SDKs and others), adding 1.9 MB and 5 ms of main-thread time.

Other Google APIs/SDKs costs a phone 0 ms of main-thread work and 1.8 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.

Desktop scores 87 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Your largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Zur optimalen Gestaltung und fortlaufenden Verbesserung uns…”.

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

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your homepage downloads 4.3 MB in 154 requests on a phone: images 1.8 MB (24), scripts 1.3 MB (78) and other files 958 KiB (48). Under 2 MB keeps phones on slow connections fast.

Sy5sB0VB4mTSZgQjIhLYyj7THBzn6RSBojTg4zE_4cOBKkL_F3x7vIY08cBs 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 1.23 g of CO₂e: 147.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Heading levels should only increase by one: 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 contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is only 45 characters: “Duschkabinen, Duschwannen, Badewannenaufsätze”. 70 to 160 characters is enough to sell the click.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 132 pages on schulte.de and 24 external pages.

There is no https://www.schulte.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://www.schulte.de/duschkabine/~Serien:Diora and https://www.schulte.de/duschkabine/~ExpressPlus:Ja all use the title “Duschkabinen | Schulte Home”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.schulte.de/duschkabine/~Serien:SCHONER+WOHNENKollektion+Duschkabinen and https://www.schulte.de/duschkabine/~ExpressPlus:Ja have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.schulte.de/duschkabine/~Serien:Diora, https://www.schulte.de/sonderposten-duschkabine-guenstig-dusche-kaufen and https://www.schulte.de/dusche-sanieren_duschabdichtung_dusche-einbauen use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.schulte.de/sonderposten-duschkabine-guenstig-dusche-kaufen, whose canonical is https://www.schulte.de/dusche-kaufen_duschkabine-guenstig. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.schulte.de/duschkabine, https://www.schulte.de/duschkabine/~Serien:Diora, https://www.schulte.de/duschkabine/~Serien:Davita, https://www.schulte.de/duschkabine/~Serien:MasterClass, https://www.schulte.de/duschkabine/~Serien:Garant+20 and https://www.schulte.de/duschkabine/~Serien:Trend+20 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.schulte.de/duschkabine/~Serien:Alexa+Style+20 and https://www.schulte.de/duschkabine/~ExpressPlus:Ja took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 122 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 404 ()”.

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.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Analytics (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 1 cookie (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.