tchibo.us website review

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

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

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

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

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

8 third-party services load with your homepage (Clarity, Shopify and Google CDN and others), adding 565 KiB and 137 ms of main-thread time.

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

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

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

Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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.

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

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 44 pages on tchibo.us and 9 external pages.

Your homepage links to /pages/tchibo-decaf-coffees, which answers with an error. Visitors hit a dead end and search engines drop it.

/pages/price-match-policy and /policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/the-tchibo-faq, /pages/ownership-and-care, /collections/all-coffee, /pages/contact, /pages/coffee-academy and /pages/price-match-policy and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/all-coffee has 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 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “klaviyo.init is not a function”.

1 link from your homepage to your own site is broken, for example https://tchibo.us/pages/tchibo-decaf-coffees (404).

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.

tchibo.us 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.

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

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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