123schlafen.de website review

Your mobile performance score is 74 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Cookiebot and others), adding 781 KiB and 460 ms of main-thread time.

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

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

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

9 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Junge Frau streckt sich lächelnd nach dem Aufwachen in ihre…”.

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

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

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

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

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

Your homepage downloads 2.1 MB in 180 requests on a phone: scripts 952 KiB (59), other files 696 KiB (76) and images 242 KiB (16). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example herz_logo.png at 452 px wide, shown at 48 px. Resized copies would save about 46 KiB.

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

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

Your title is only 14 characters: “123schlafen.de”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Schlafen neu erleben.” and “Sie haben eine Pension, ein Hotel oder eine ander…”). One clear main headline is easier for people and search engines.

The homepage links to 38 pages on 123schlafen.de and 0 external pages.

/collections/matratzen, /collections/topper, /collections/lattenroste, /collections/bettwaren, /pages/kontakt and /pages/ruckgaberichtlinien and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

123schlafen.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

DMARC is set to p=none, so mail pretending to be 123schlafen.de is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.