manukadoctor.nl website review

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

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

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 (Shopify, Yotpo and Klaviyo and others), adding 1.4 MB and 818 ms of main-thread time.

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

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

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

Yotpo costs a phone 209 ms of main-thread work and 350 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,599 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

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

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

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

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Echte Manukahoning, rechtstreeks uit Nieuw-Zeeland”.

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

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

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

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

Your homepage downloads 3.4 MB in 385 requests on a phone: scripts 1.1 MB (138), other files 1,021 KiB (149) and images 751 KiB (55). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example M-Doc_340_MGO_UK_250g_Front_Web.jpg at 1,000 px wide, shown at 60 px. Resized copies would save about 199 KiB.

2 images (87 KiB) are 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.

4 images further down the page (118 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

All page content should be contained by landmarks: 23 elements on the page fail 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 visible links have no text or label, so screen readers cannot say where they go.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 76 characters, so Google will cut it off around 60: “Manuka Doctor: Authentieke Manuka honing & Huidverzorging - Manuka Doctor NL”.

There are 3 <h1> headlines (“”, “Echte Manukahoning, rechtstreeks uit Nieuw-Zeeland” and “Dat zeggen gezondheidsdeskundigen.”). One clear main headline is easier for people and search engines.

9 links have no real href, so search engines can't follow them.

The homepage links to 80 pages on manukadoctor.nl and 20 external pages.

https://www.manukadoctor.nl/collections/voordeel-packs, https://www.manukadoctor.nl/collections/overige-producten, https://www.manukadoctor.nl/pages/rewards and https://www.manukadoctor.nl/blogs/content have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.manukadoctor.nl/pages/rewards and https://www.manukadoctor.nl/blogs/content have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 images failed to load on a phone, for example https://www.manukadoctor.nl/.

5 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

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

1 image is served at too low a resolution for sharp phone screens.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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