Website review, no card needed
ivn.nl website review
Visit site (opens in a new tab)Reviewed 1 November 202633 issues · 84 checks
This review found 33 issues worth fixing on ivn.nl, 7 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 704 ms |
| May 16, 2026 | 699 ms |
| May 23, 2026 | 706 ms |
| May 30, 2026 | 710 ms |
| Jun 6, 2026 | 727 ms |
| Jun 13, 2026 | 732 ms |
| Jun 20, 2026 | 729 ms |
| Jun 27, 2026 | 720 ms |
| Jul 4, 2026 | 708 ms |
| Jul 11, 2026 | 690 ms |
| Jul 18, 2026 | 705 ms |
| Jul 25, 2026 | 713 ms |
| Aug 1, 2026 | 723 ms |
| Aug 8, 2026 | 733 ms |
| Aug 15, 2026 | 748 ms |
| Aug 22, 2026 | 738 ms |
| Aug 29, 2026 | 735 ms |
| Sep 5, 2026 | 746 ms |
| Sep 12, 2026 | 753 ms |
| Sep 19, 2026 | 776 ms |
| Sep 26, 2026 | 786 ms |
| Oct 3, 2026 | 787 ms |
| Oct 10, 2026 | 772 ms |
| Oct 17, 2026 | 775 ms |
| Oct 24, 2026 | 772 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 115 ms |
| May 16, 2026 | 114 ms |
| May 23, 2026 | 116 ms |
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 116 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 117 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 147 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 155 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 178 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
1.9 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Use efficient cache lifetimes
1.0 s · 701 KiB26 files are served with short cache lifetimes, so returning visitors download them again (701 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 1.5 MB and 2.0 s of main-thread time.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 824 ms
824 msGoogle Tag Manager costs a phone 824 ms of main-thread work and 678 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.
Reduce unused JavaScript
799 KiBAbout 799 KiB of JavaScript is downloaded but never used on this page.
Facebook adds 515 ms
515 msFacebook costs a phone 515 ms of main-thread work and 355 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.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 328 ms
328 msGoogle Maps costs a phone 328 ms of main-thread work and 344 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 349 ms. During a long task the page ignores taps.
Improve image delivery
186 KiB2 images could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.6 s
17.6 sThe page becomes fully interactive after 17.6 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 115 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.171
0.171The layout shifts by 0.171 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ontdek wat 10 minuten natuur met je doet. Ga even groen >>”.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 386 ms
386 msReal visitors wait 386 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.2 MB in 132 requests
2.2 MBYour homepage downloads 2.2 MB in 132 requests on a phone: scripts 1.7 MB (55), images 273 KiB (17) and fonts 143 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
62 KiB1 image is downloaded at several times the size a phone draws it, for example maxresdefault.jpg at 1,280 px wide, shown at 359 px. Resized copies would save about 62 KiB.
1 image in older formats
1 image (212 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.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Hidden but focusable
19 elements hidden from screen readers can still receive keyboard focus.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
201 internal links, 17 external
The homepage links to 201 pages on ivn.nl and 17 external pages.
8 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “IVN Natuureducatie laat kinderen en volwassenen beleven hoe leuk, gezond én belangrijk natuur is. Doe je mee? Bezoek on…”.
One H1 headline
Your main headline reads: “Wat wil je doen in de natuur?”.
Title: 43 characters
Your title is a healthy 43 characters: “Samen brengen we de natuur dichterbij - IVN”.
Canonical URL set
The canonical URL is https://www.ivn.nl/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.ivn.nl/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.ivn.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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,098 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.ivn.nl/aanbod/vervolgonderwijs and https://www.ivn.nl/aanbod/jongvolwassenen/home all use the title “Home - IVN”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://www.ivn.nl/aanbod/vervolgonderwijs, https://www.ivn.nl/aanbod/jongvolwassenen/home, https://www.ivn.nl/provincies, https://www.ivn.nl/aanbod/veldhoeve and https://www.ivn.nl/aanbod/natuurschool/lauwersoog have no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.ivn.nl/aanbod/kinderopvang/home, whose canonical is https://www.ivn.nl/aanbod/kinderopvang. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages slow to respond
https://www.ivn.nl/aanbod/kinderopvang/home, https://www.ivn.nl/aanbod/vervolgonderwijs, https://www.ivn.nl/aanbod/jongvolwassenen/home, https://www.ivn.nl/aanbod/gemeenten/home, https://www.ivn.nl/aanbod/de-zorg/home and https://www.ivn.nl/aanbod/toerisme-recreatie/home and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'top')”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
12 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 264 words of copy
The homepage carries about 264 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact”.
3 short forms
3 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ivn.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Team Blue Carrier Limited
Company
- Headquarters
- Amsterdam
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on ivn.nl, including 17 speed issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.