labfresh.nl website review

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and LoyaltyLion and others), adding 1.5 MB and 465 ms of main-thread time.

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

About 318 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

LoyaltyLion costs a phone 83 ms of main-thread work and 358 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.

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

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

38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 10.0 MB in 343 requests on a phone: media 5.9 MB (2), images 1.7 MB (102) and scripts 1.2 MB (131). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example de_Volkskrant_Logo_3b4b8f1f-72c9-4ff0-930b-a85ff06739c4.png at 5,000 px wide, shown at 150 px. Resized copies would save about 107 KiB.

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

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

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

ARIA role should be appropriate for the element: 163 elements on the page fail this check, rated minor by axe-core.

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

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://labfresh.nl)”.

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

The homepage links to 430 pages on labfresh.nl and 42 external pages.

Your Organization JSON-LD is missing logo, 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://labfresh.co/collections/fresh-from-the-lab, https://labfresh.co/collections/shkodran-mustafi-x-labfresh-collection, https://labfresh.co/collections/autumn-winter-26, https://labfresh.co/collections/the-bestsellers and https://labfresh.co/collections/bundles have no meta description, so Google writes the search snippet from whatever text it finds.

https://labfresh.co/collections/allproducts, https://labfresh.co/collections/fresh-from-the-lab, https://labfresh.co/collections/lasse-schone-x-labfresh, https://labfresh.co/collections/shkodran-mustafi-x-labfresh-collection, https://labfresh.co/collections/autumn-winter-26 and https://labfresh.co/collections/the-bestsellers and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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: 4 trust badges. 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.

The homepage carries about 665 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 20 cookies (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 53 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.