webyes.nl
Yes, this site meets the WebYes certification
The average is at least 80 and no pillar is below 60.
Better than 69% of the 29 scanned sites · methodology
Certified on 8 October 2026 · 15 pages checked · 4 improvements found
- SpeedCan improveBetter than 48% (national)
- SecurityCan improveBetter than 77% (national)
- MobileIn orderBetter than 7% (national)
- AccessibilityIn orderBetter than 79% (national)
Machine-readable verification: /api/verify/webyes.nl
Fix this first
These findings raise the score fastest: pillars under the floor of 60 first, then by severity and distance to 80.
- WarningSpeed
3 render-blocking <link rel="stylesheet"> in <head> (target: ≤2).
How to fix it
Reduce render-blocking CSS: inline the critical above-the-fold styles and load the rest asynchronously. Also remove CSS that is no longer used anywhere.
For the developer: Inline critical CSS, lazy-load the rest with the `<link rel="preload" as="style" onload="this.rel='stylesheet'">` pattern, or split chunks per route. Each blocking stylesheet adds round-trips to LCP.
- WarningSecurity
Sensitive path reachable: /admin/ (HTTP 200, 16882 bytes).
How to fix it
A sensitive path is publicly reachable (such as a .env file, .git folder or admin panel). Block the path at the server level or take the file offline, and rotate any leaked keys.
For the developer: Block the path at the reverse proxy (deny .git/.env/etc.), remove the file from the deploy artifact, and rotate any secrets that may have been exposed.
- WarningSecurity
No Content-Security-Policy header — XSS / clickjacking surface is wide open.
How to fix it
Add a Content-Security-Policy header that defines which sources may load scripts and styles. Start with a report-only policy if needed and tighten it from there.
For the developer: Start with a strict-dynamic CSP using nonces: `Content-Security-Policy: script-src 'nonce-<...>' 'strict-dynamic'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'`. Roll out in `Content-Security-Policy-Report-Only` first to catch violations.
All findings per pillar
- 0 critical
- 1 error
- 3 warning
- 0 info
Speed1 findingscore 70
- WarningSpeed
3 render-blocking <link rel="stylesheet"> in <head> (target: ≤2).
How to fix it
Reduce render-blocking CSS: inline the critical above-the-fold styles and load the rest asynchronously. Also remove CSS that is no longer used anywhere.
For the developer: Inline critical CSS, lazy-load the rest with the `<link rel="preload" as="style" onload="this.rel='stylesheet'">` pattern, or split chunks per route. Each blocking stylesheet adds round-trips to LCP.
Security2 findingsscore 78
- WarningSecurity
Sensitive path reachable: /admin/ (HTTP 200, 16882 bytes).
How to fix it
A sensitive path is publicly reachable (such as a .env file, .git folder or admin panel). Block the path at the server level or take the file offline, and rotate any leaked keys.
For the developer: Block the path at the reverse proxy (deny .git/.env/etc.), remove the file from the deploy artifact, and rotate any secrets that may have been exposed.
- WarningSecurity
No Content-Security-Policy header — XSS / clickjacking surface is wide open.
How to fix it
Add a Content-Security-Policy header that defines which sources may load scripts and styles. Start with a report-only policy if needed and tighten it from there.
For the developer: Start with a strict-dynamic CSP using nonces: `Content-Security-Policy: script-src 'nonce-<...>' 'strict-dynamic'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'`. Roll out in `Content-Security-Policy-Report-Only` first to catch violations.
Accessibility1 findingscore 96
- ErrorAccessibilityAutomatically checked
Page has 2 <main> elements without distinct aria-labels.
How to fix it
The page has more than one <main> element (or role="main"). Keep exactly one; multiple main content areas confuse screen readers.
For the developer: When using multiple <main> landmarks, give each a unique aria-label: <main aria-label="Primary content">.
Score over time
Every audit and re-audit counts: this is the average score per scan day.
Scan timeline
Pillar scores across recent scans. Methodology changes (different engine version) are noted on the point.
8 October 2026 · Full audit
86Speed 70Security 78Mobile 100Accessibility 967 September 2026 · Full audit
88Speed 77Security 76Mobile 100Accessibility 1008 August 2026 · Full audit
88Speed 77Security 76Mobile 100Accessibility 998 July 2026 · Full audit
94Speed 100Security 79Mobile 100Accessibility 97
Full certification report
Part of the WebYes certification: beyond the four pillars we also audit SEO, structured data, content, links, privacy and AI findability. These extra categories do not count towards the certification score.
Pages examined
Sample of 15 pages (not every URL on the site).
- https://webyes.nl/
- https://webyes.nl/werkwijze
- https://webyes.nl/kennisbank/core-web-vitals
- https://webyes.nl/kennisbank/ssl-certificaat
- https://webyes.nl/kennisbank/website-snelheid-testen
- https://webyes.nl/kennisbank/security-headers
- https://webyes.nl/kennisbank/mobielvriendelijke-website
- https://webyes.nl/kennisbank/digitale-toegankelijkheid
- https://webyes.nl/kennisbank/wcag
- https://webyes.nl/register
- https://webyes.nl/contact
- https://webyes.nl/kennisbank
- https://webyes.nl/blog
- https://webyes.nl/about
- https://webyes.nl/prijzen
Diff vs previous audit
7 September 2026 → 8 October 2026
Resolved (1)
- Missing `Cross-Origin-Opener-Policy` + `Cross-Origin-Embedder-Policy`. Cross-origin isolation lets you use SharedArrayBuffer and high-resolution timers safely.https://webyes.nl/
New (1)
- Page has 2 <main> elements without distinct aria-labels.https://webyes.nl/kennisbank/core-web-vitals
Additional categories: 13 findings
- ErrorTechnical
7 of 18 prose strings in the RSC flight payload never appear in the rendered HTML (e.g. "De pagina die u zoekt bestaat niet of is verplaatst.", "Vier pijlers: snelheid (Core Web Vitals, TTFB), veiligheid (SSL, headers, bekende CVE's), …"). That content is invisible to AI crawlers and to Google's first-pass HTML fetch.
How to fix it
For the developer: Server-render this content: remove client-only mount gates (idle/IntersectionObserver deferred-mount wrappers, `useState(false)` + effect flips) and `next/dynamic` with `ssr: false` around content sections; keep `next/dynamic` (default ssr: true) for code-splitting. Accordions/tabs must keep collapsed text in the DOM (Radix `forceMount`, native <details>). Verify with view-source: the copy must appear outside <script> tags.
- WarningOn-page SEO
0/4 images are missing alt attributes.
How to fix it
For the developer: Add a descriptive `alt="..."` for every <img>. Use `alt=""` only for purely decorative images.
- WarningOn-page SEO
Hreflang "en" points at host "webyes.nl" (expected locale "nl" for this ccTLD).
How to fix it
For the developer: Serve each hreflang alternate on a host whose ccTLD matches the language, or use a language-neutral host with matching path prefixes.
- WarningStructured data
Schema "Product" is missing required property: image (affects 1 page).
How to fix it
For the developer: Fix the JSON-LD generator that emits this Product block — one fix eliminates 1 occurrence(s). JSON-LD path: <root>. Affected URLs: https://webyes.nl/prijzen.
- WarningStructured data
6 of 7 FAQPage answers in JSON-LD never appear in the rendered HTML (first: "Wat wordt er precies gescand?"). Google requires marked-up content to be visible on the page.
How to fix it
For the developer: Render the FAQ answers in the server HTML. If a client-only mount hides the whole section, remove the gate (or `ssr: false`); if an accordion unmounts collapsed panels, keep them in the DOM (Radix `forceMount` + CSS-hidden closed state, or native <details>/<summary>). Collapsed-but-present answers are fine; the text just has to exist outside <script> tags.
- WarningContent
13 pages share the title template "… | WebYes" with distinct left/right tokens (below near-clone Jaccard).
How to fix it
For the developer: Differentiate titles beyond a shared brand/site suffix or prefix. Examples: https://webyes.nl/, https://webyes.nl/about, https://webyes.nl/blog, https://webyes.nl/kennisbank/core-web-vitals, https://webyes.nl/kennisbank/digitale-toegankelijkheid (+8 more).
- WarningSpam signals
Term "gekeurd" appears unusually often (14×, 6% of words).
How to fix it
For the developer: Rewrite for natural language — repeated exact-match phrases can trigger spam classifiers.
- InfoOn-page SEO
H1 is slightly over the recommended length (22 chars, max undefined).
How to fix it
For the developer: Trim the H1 toward a short heading if the extra words are body copy rather than the page topic.
- InfoOn-page SEO
Heading level jumps from h1 to h3, skipping h2.
- InfoContent
Text-to-HTML ratio is 0.8% (target ≥ 2%).
How to fix it
For the developer: Very low ratios usually mean the hydration payload, inline RSC blob or a vendor script is bigger than the rendered prose. Inspect the largest scripts and externalise or split them.
- InfoTechnical
1 crawled page(s) are not listed in any sitemap.
How to fix it
For the developer: Add these URLs to your sitemap or noindex them. Example: https://webyes.nl/prijzen
- InfoTechnical
No HTML sitemap link found on the homepage. Placing one in the footer is an industry best practice for UX and crawler/AI discovery.
How to fix it
For the developer: Add a link to a user-facing HTML sitemap (e.g. `/sitemap`, not `sitemap.xml`) inside the <footer>. An HTML sitemap acts as a structural overview for lost visitors and as a fallback discovery surface for search engines and AI crawlers.
- InfoQuality impression
Homepage has no `<link rel="icon">` — browsers will request /favicon.ico which may 404.
How to fix it
For the developer: Add a custom favicon that reflects your brand. A missing favicon causes extra 404 log noise and looks unprofessional in browser tabs and bookmarks.
More from the register
Other websites holding an active WebYes certification. Every report is public and audited on the same four pillars.