purition.eu website review

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

FontAwesome CDN costs a phone 1.2 s of main-thread work and 102 KiB 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 4.2 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (FontAwesome CDN, Optanon and Klaviyo and others), adding 2.0 MB and 1.6 s of main-thread time.

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

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

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

Shopify costs a phone 33 ms of main-thread work and 1.3 MB 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.

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

About 203 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

11 KiB could be saved by minifying JavaScript.

6 KiB JavaScript is shipped twice across bundles.

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 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A whole lot better We believe in the power of good, whole f…”.

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

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

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

20 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-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 281 requests on a phone: images 1.9 MB (31), other files 1.1 MB (152) and scripts 813 KiB (75). Under 2 MB keeps phones on slow connections fast.

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

1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

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

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

Your title is 72 characters, so Google will cut it off around 60: “Natural Protein Powders & Meal Replacements - Fitness Food – Purition UK”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 58 pages on purition.eu and 27 external pages.

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

https://www.purition.com/collections/accessories is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.purition.com/pages/shop-range, https://www.purition.com/pages/about-purition and https://www.purition.com/pages/b-corp 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 https://www.purition.com/blogs/articles/green-credentials, whose canonical is https://www.purition.com/blogs/inside-purition/green-credentials. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.purition.com/pages/shop-range, https://www.purition.com/collections/purition-wholefood-bags, https://www.purition.com/collections/purition-wholefood-sachets, https://www.purition.com/collections/purition-vegan-wholefood-bags, https://www.purition.com/collections/purition-vegan-wholefood-sachets and https://www.purition.com/collections/flavoured-protein-powder and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

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

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.

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,619 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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