livefresh.de website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, ablyft.com and Klaviyo and others), adding 2.2 MB and 1.5 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page.

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

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

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

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

Klaviyo costs a phone 237 ms of main-thread work and 511 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.

Reviews.io costs a phone 197 ms of main-thread work and 386 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.

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

3 images could be 37 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

13 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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.

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.

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

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Saftkur auf wissenschaftlicher Basis – empfohlen von Ivana …”.

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

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

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

Real visitors wait 222 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 5.9 MB in 471 requests on a phone: scripts 3.3 MB (193), other files 1.6 MB (205) and images 392 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

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

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Elements with visible text labels do not have matching accessible names. (20 elements).

1 link has no real href, so search engines can't follow it.

The homepage links to 98 pages on livefresh.de and 14 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://livefresh.de/pages/livefresh-10-jahre-jubilaum is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://livefresh.de/policies/shipping-policy, https://livefresh.de/pages/livefresh-10-jahre-jubilaum and https://livefresh.de/pages/ballaststoff-saftkur have no meta description, so Google writes the search snippet from whatever text it finds.

https://livefresh.de/pages/skyr-protein-drink has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=26126929&tm=gtm002&Ver=2&mid=d087617f-5b0c-4c48-878f-dddedfd015d8&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Kaltgepresste%20Saftkuren,%20Shots%20%26%20Fe.

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

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://livefresh.de/cdn/shop/t/752/assets/section-included-items.css?v=209374' because it…”.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Klaviyo, Microsoft Ads and Pinterest Tag 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 22 cookies, 1 of them by other companies (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 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.