primalharvest.de website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Cookie-Script.com and Clarity and others), adding 2.7 MB and 2.0 s of main-thread time.

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

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

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

kodif.ai costs a phone 127 ms of main-thread work and 303 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.

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

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

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

32 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

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

Your homepage downloads 6.0 MB in 387 requests on a phone: scripts 3.2 MB (139), images 1.3 MB (17) and other files 1.2 MB (208). Under 2 MB keeps phones on slow connections fast.

1 image (49 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.

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

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

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.

Your meta description is only 58 characters: “Natürliche Kräutermischungen, Vitamine, Kollagen und mehr.”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Dein Neuanfang beginnt hier.” and “Dein Neuanfang beginnt hier.”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 3 problems, for example “Organization: url is not an absolute URL ("primalharvest.de")”.

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

The homepage links to 45 pages on primalharvest.de and 5 external pages.

The HTML your server sends has 839 of the 2,519 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

https://primalharvest.de/pages/ingredients and https://primalharvest.de/pages/order-tracking are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://primalharvest.de/pages/uber-uns, https://primalharvest.de/blogs/posts, https://primalharvest.de/pages/help-center, https://primalharvest.de/pages/stay-ai-subscription, https://primalharvest.de/collections/all and https://primalharvest.de/pages/ingredients and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://primalharvest.de/blogs/posts, https://primalharvest.de/pages/help-center, https://primalharvest.de/pages/stay-ai-subscription, https://primalharvest.de/pages/werde-produkttester-in and https://primalharvest.de/pages/cookies have no <h1> headline, so visitors and search engines get no clear main topic.

https://primalharvest.de/pages/stay-ai-subscription, https://primalharvest.de/collections/balance, https://primalharvest.de/pages/werde-produkttester-in and https://primalharvest.de/pages/cookies have 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 21 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=26018440&tm=gtm002&Ver=2&mid=3d7cb7fc-a6b3-4a71-a0d3-0ca8305607a6&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Primal%20Harvest%20-%20Primal%20Harvest&p=htt.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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