ontmoeting.nl website review

About 940 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

32 files are served with short cache lifetimes, so returning visitors download them again (1,008 KiB).

2 images could be 538 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 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 7.4 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Vimeo and others), adding 41.3 MB and 1.8 s of main-thread time.

Vimeo costs a phone 237 ms of main-thread work and 39.8 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.

Google CDN costs a phone 680 ms of main-thread work and 736 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.

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

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

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

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

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

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

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.

Your largest element takes 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We gebruiken cookies om content en advertenties te personal…”. Most of its time is element render delay (7.9 s).

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

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

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

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

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

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 105 ms to 105 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 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 42.5 MB in 84 requests on a phone: other files 39.6 MB (29), scripts 1.9 MB (23) and images 854 KiB (16). Under 2 MB keeps phones on slow connections fast.

2 images (570 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.

2 images are downloaded at several times the size a phone draws them, for example 20211110-Ontmoeting-Post-Francisco-voetbalclinic-1758-1920x1 at 1,920 px wide, shown at 360 px. Resized copies would save about 146 KiB.

2 images further down the page (246 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 12.05 g of CO₂e: 1446.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail 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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 27 characters: “Home - Stichting Ontmoeting”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 80 pages on ontmoeting.nl and 7 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.ontmoeting.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.ontmoeting.nl/locaties, https://www.ontmoeting.nl/werkenbij, https://www.ontmoeting.nl/vrijwilliger, https://www.ontmoeting.nl/client, https://www.ontmoeting.nl/ik-zoek-hulp and https://www.ontmoeting.nl/ik-ben-verwijzer and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ontmoeting.nl/client, https://www.ontmoeting.nl/ik-zoek-hulp, https://www.ontmoeting.nl/ons-hulpaanbod, https://www.ontmoeting.nl/hulpaanbod/ambulantebegeleiding, https://www.ontmoeting.nl/hulpaanbod/wonen and https://www.ontmoeting.nl/hulpaanbod/beschermdwonen and 1 other took over 3 s to send their HTML from our server.

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

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

Chrome logged issues while loading the page (“Cookie”).

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

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

Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (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 3 cookies, 2 of them by other companies (measured from a US location before any click).

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