primalharvest.it website review

Google Tag Manager costs a phone 1.3 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.

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and kodif.ai and others), adding 2.6 MB and 2.1 s of main-thread time.

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

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

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

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

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

kodif.ai costs a phone 144 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.

OptiMonk costs a phone 61 ms of main-thread work and 332 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.

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

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

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

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

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 34.0 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 6.2 MB in 503 requests on a phone: scripts 3.2 MB (157), other files 1.7 MB (299) and images 1.0 MB (18). 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.76 g of CO₂e: 211.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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.

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

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.it")”.

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

The homepage links to 44 pages on primalharvest.it and 6 external pages.

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.it/pages/ingredients and https://primalharvest.it/pages/order-tracking are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

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

https://primalharvest.it/pages/stay-ai-subscription, https://primalharvest.it/pages/werde-produkttester-in and https://primalharvest.it/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=6713935a-a753-4b52-b84f-c4028414196b&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Primal%20Harvest%20-%20Primal%20Harvest&p=htt.

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

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