prolon.nl website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Facebook and others), adding 1.9 MB and 1.6 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 426 ms of main-thread work and 544 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.

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

Hotjar costs a phone 330 ms of main-thread work and 65 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.

Facebook costs a phone 250 ms of main-thread work and 231 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 167 ms of main-thread work and 316 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 127 ms of main-thread work and 347 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 221 ms. During a long task the page ignores taps.

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

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

5 KiB could be saved by minifying CSS.

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

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

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

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

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 4.6 MB in 376 requests on a phone: scripts 2.4 MB (184), other files 1.1 MB (139) and images 504 KiB (28). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Frame_1321322778.jpg at 1,200 px wide, shown at 320 px. Resized copies would save about 43 KiB.

1 image (89 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.30 g of CO₂e: 155.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

3 images have no alt text, which hurts accessibility and image search.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Headings skip levels (h1 → h3 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 meta description is only 61 characters: “Fasting Mimicking Diet voor een betere jij in slechts 5 dagen”. 70 to 160 characters is enough to sell the click.

The homepage links to 172 pages on prolon.nl and 4 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://prolon.nl/products/prolon-5-dag, https://prolon.nl/products/opnieuw-instellen, https://prolon.nl/products/prolon-vastenshake, https://prolon.nl/products/prolon-vasten-bar, https://prolon.nl/products/prolon-levensduur-spreiding and https://prolon.nl/products/prolon-l-bioom have no <h1> headline, so visitors and search engines get no clear main topic.

https://prolon.nl/products/prolon-5-dag, https://prolon.nl/pages/internationalebestellingen, https://prolon.nl/products/opnieuw-instellen, https://prolon.nl/products/prolon-vastenshake, https://prolon.nl/products/prolon-vasten-bar and https://prolon.nl/products/prolon-levensduur-spreiding and 1 other took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56271068&Ver=2&mid=d4d65892-98cb-4396-b1a2-c76b7b0e89e9&bo=1&sid=b79187c0dc0511f19bfa5957d0315598&vid=b7918eb0dc0511f1b14221dfd508eef0&vids=1&msclkid=N&pi=918639831&lg.

5 of 18 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 “SyntaxError: Failed to execute 'querySelector' on 'Document': '.menu-section-component[data-menu-id="menu-over "]' is n…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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 29 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.