teegschwendner.de website review

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

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

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

8 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and PayPal and others), adding 1.1 MB and 1.6 s of main-thread time.

Usercentrics CMP costs a phone 893 ms of main-thread work and 260 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.

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

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

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

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

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

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

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

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need.

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.

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.

Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Gemütliche Teestunden Herbsttees entdecken Teegeschenk find…”.

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

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

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

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

The layout shifts by 0.274 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 2.7 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-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

13 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 3.2 MB in 170 requests on a phone: scripts 1.5 MB (100), images 883 KiB (20) and fonts 538 KiB (7). Under 2 MB keeps phones on slow connections fast.

9 images (580 KiB) are 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.

8 images further down the page (486 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

6 images are downloaded at several times the size a phone draws them, for example im-bag.jpg at 500 px wide, shown at 154 px. Resized copies would save about 57 KiB.

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

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

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

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Gemütliche Teestunden”, “Teeleidenschaft” and “Schnell zum Lieblingstee”). One clear main headline is easier for people and search engines.

The homepage links to 142 pages on teegschwendner.de and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /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.

/wishlist/index is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/wishlist/index, /Matcha and /UEber-uns have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /StoreLocator, whose canonical is /Filialfinder. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/StoreLocator, /Tee, /Matcha, /Gutscheine, /Fachgeschaefte and /Tee/Matcha-Tee have no <h1> headline, so visitors and search engines get no clear main topic.

/Tee/Matcha-Tee took over 3 s to send its HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d21m4dsqdd3b9h.cloudfront.net/tgs835e/search/templates/main/deployment/1786535099/…”.

http://teegschwendner.de does not redirect to https, so some visitors land on the insecure version.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

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

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

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

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 and Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

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

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