7oclock.de website review

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

24 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 1.2 MB and 697 ms of main-thread time.

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

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

40 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (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.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

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.

Real visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 37.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kunstblumenstrauß Forest Ember in Bordeaux, Grün & Braun au…”.

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

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

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

Real visitors wait 3.9 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-24, real Chrome visitors' tap response (inp) went from 96 ms to 168 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.1 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.6 MB in 467 requests on a phone: images 3.5 MB (103), scripts 1.9 MB (133) and fonts 1.9 MB (50). Under 2 MB keeps phones on slow connections fast.

Haven-Bettwaesche-dunkelbraun-neu-Moodbild_5.png 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).

1 image (72 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

5 images further down the page (107 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 2.44 g of CO₂e: 293.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Elements must only use permitted ARIA attributes: 24 elements on the page fail this check, rated serious by axe-core.

5 tap targets are too small or too close together to hit reliably with a finger.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

24 visible links have no text or label, so screen readers cannot say where they go.

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

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

The homepage links to 503 pages on 7oclock.de and 3 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/pages/uber-uns, /pages/retourenportal, /pages/hilfe-kontakt, /policies/privacy-policy, /collections/neuheiten and /collections/bestseller and 9 others all use the title “PayPal”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/uber-uns, /pages/retourenportal, /pages/hilfe-kontakt and /policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/neuheiten, /collections/bestseller, /collections/spare-im-set, /collections/letzte-chance, /collections/alle-produkte and /collections/kueche and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 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 ()”.

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

1 link go through two or more redirects, for example https://shopify.com/56512544851/account.

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.

7oclock.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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 72 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

DMARC is set to p=none, so mail pretending to be 7oclock.de is still delivered. Reports are on, so moving to quarantine is the next step.

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, Hotjar and Klaviyo and 3 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 24 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.