schoonenberg.nl website review

45 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

8 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.2 s faster on a phone.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

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

Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

ZenDesk costs a phone 216 ms of main-thread work and 431 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 255 ms. During a long task the page ignores taps.

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

About 24 KiB of CSS is downloaded but never applied on this page.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.

Your largest element takes 16.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “profiteer-2025-mobiel.jpg”.

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

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

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

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

Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 242 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.7 MB in 144 requests on a phone: scripts 2.7 MB (62), images 1.6 MB (13) and other files 185 KiB (58). Under 2 MB keeps phones on slow connections fast.

fbb21c54528fde0d2704064534357f5383d6cbe1.png weighs 742 KiB. On a phone connection a single image that size takes seconds.

7 images (1.2 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.

fbb21c54528fde0d2704064534357f5383d6cbe1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images are downloaded at several times the size a phone draws them, for example keyvisual-eon-couple-at-table.jpg at 1,600 px wide, shown at 346 px. Resized copies would save about 115 KiB.

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

17 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 3)”.

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

The homepage links to 113 pages on schoonenberg.nl and 12 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.

https://www.schoonenberg.nl/phonak-eon, https://www.schoonenberg.nl/phonak-eon-hoortoestellen and https://www.schoonenberg.nl/audionova-toestellen have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.schoonenberg.nl/service-contact/contact-formulier and https://www.schoonenberg.nl/phonak-eon-hoortoestellen have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.schoonenberg.nl/afspraak has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.schoonenberg.nl/phonak-eon, https://www.schoonenberg.nl/audionova-toestellen, https://www.schoonenberg.nl/hoortoestellen/luidspreker-in-het-oor-hoortoestellen and https://www.schoonenberg.nl/hoortoestellen/in-het-oor-hoortoestellen took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://bat.bing.net/action/0?ti=163012569&Ver=2&mid=ea96a326-78ea-41fd-9475-0020c58cdacf&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Schoonenberg%3A%20Sinds%201926%20d%C3%A9%20expert%20in.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Tag Manager, Hotjar 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 22 cookies (measured from a US location before any click).

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