ronnefeldt.com website review

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

26 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

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

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

Reduce initial server response time. Google estimates savings of 2.4 s on a phone.

The HTML itself could arrive about 2.4 s sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

Your server takes 2.5 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

Usercentrics CMP costs a phone 356 ms of main-thread work and 193 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.3 s on main-thread work while loading, 907 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Google CDN costs a phone 105 ms of main-thread work and 347 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.

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

28 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 16 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.

For real visitors the layout shifts by 0.66 (75th percentile). Good is under 0.1.

Your largest element takes 36.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GUTSCHEINCODE: ZEITFÜRTEE”.

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

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

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

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

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

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

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

Your homepage downloads 8.0 MB in 146 requests on a phone: images 3.4 MB (91), fonts 3.1 MB (8) and scripts 1.3 MB (27). Under 2 MB keeps phones on slow connections fast.

35 images (2.1 MB) 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.

3 images are downloaded at several times the size a phone draws them, for example Startseite_Kategorie_Loser-Tee_1560x600_mobil.jpg at 1,560 px wide, shown at 410 px. Resized copies would save about 142 KiB.

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

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

1 link inside paragraphs relies on colour alone to stand out.

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

18 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

The homepage links to 219 pages on ronnefeldt.com and 5 external pages.

There is no https://www.ronnefeldt.com/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.ronnefeldt.com/teeshop/de/shop and https://www.ronnefeldt.com/teeshop/de all use the title “Tee online kaufen | Ronnefeldt® Tee Shop”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ronnefeldt.com/teeshop/de/shop and https://www.ronnefeldt.com/teeshop/de use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.ronnefeldt.com/teeshop/de/shop, whose canonical is https://www.ronnefeldt.com/teeshop/de. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ronnefeldt.com/teeshop/de/shop/loser-tee/schwarzer-tee, https://www.ronnefeldt.com/teeshop/de/shop/loser-tee/aromatisch-schwarz, https://www.ronnefeldt.com/teeshop/de/shop/loser-tee/gruener-tee, https://www.ronnefeldt.com/teeshop/de/shop/loser-tee/aromatisch-gruen and https://www.ronnefeldt.com/teeshop/de/shop/loser-tee/wellness-tee took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “$(...).datepicker is not a function”.

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.

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

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

Before a visitor clicks anything, the page loads 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 3 cookies (measured from a US location before any click).

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