bewustpuur.nl website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 2.4 s.

7 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

6 third-party services load with your homepage (trengo.eu, nextchapter-ecommerce.com and Cookiebot and others), adding 5.1 MB and 435 ms of main-thread time.

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

nextchapter-ecommerce.com costs a phone 153 ms of main-thread work and 4.5 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.

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

trengo.eu costs a phone 203 ms of main-thread work and 415 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,889 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

1 file is served with short cache lifetimes, so returning visitors download them again (33 KiB).

22 KiB could be saved by minifying CSS.

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

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

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

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

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

The layout shifts by 0.126 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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 116 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.6 MB in 67 requests on a phone: images 4.2 MB (40), scripts 1.2 MB (12) and stylesheets 105 KiB (3). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

5 images (2.8 MB) 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.

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

5 dropdowns have no label.

17 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 174 pages on bewustpuur.nl and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.bewustpuur.nl/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.bewustpuur.nl/nl/mijn-favorieten has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.bewustpuur.nl/nl/nagels, https://www.bewustpuur.nl/nl/haar, https://www.bewustpuur.nl/nl/parfum, https://www.bewustpuur.nl/nl/voor-thuis, https://www.bewustpuur.nl/nl/kleding and https://www.bewustpuur.nl/nl/-kerst and 4 others took over 3 s to send their HTML from our server.

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

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

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

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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