# BeaverCheck Audit Report — https://www.pijnacker-nootdorp.nl

**Date:** November 12, 2026  
**URL:** https://www.pijnacker-nootdorp.nl  
**Overall Grade:** B (83/100)  
**Report:** https://beavercheck.com/results/7f311269-1a0a-4c70-96f3-6e7131d3f113

## Top Findings

1. **[CRITICAL]** 'unsafe-eval' found in script source — Security > Content Security Policy
2. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
3. **[WARNING]** 1 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking
4. **[WARNING]** 22 inline style attribute(s) detected — Security > CSP Inline-Style Readiness
5. **[WARNING]** 51 third-party resources (81% of weight) — Performance > Page Weight Inventory

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 51 |
| Accessibility | 100 |
| Best Practices | 96 |
| SEO | 92 |

---

## Security

### Security Headers (B — 80/100)

*7 of 10 headers properly configured*

- **[PASS]** HSTS is enabled
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[PASS]** Referrer-Policy is properly configured
- **[PASS]** Permissions-Policy is set
- **[PASS]** Content-Security-Policy is present
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[WARNING]** X-Powered-By header reveals technology stack — This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.
- **[PASS]** Server header is not present
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (F — 35/100)

*3 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[CRITICAL]** 'unsafe-inline' found in script source — 'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
- **[CRITICAL]** 'unsafe-eval' found in script source — 'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
- **[PASS]** No wildcard in script source
- **[WARNING]** object-src allows plugin content — Set object-src to 'none' to prevent Flash/Java plugin exploits.
- **[WARNING]** base-uri directive is missing — Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
- **[WARNING]** frame-ancestors directive is missing — frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
- **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking.
- **[PASS]** upgrade-insecure-requests is enabled

### TLS & Certificates (A+ — 100/100)

*TLS 1.3, 8 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[PASS]** HTTP/2 is negotiated
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 35 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 7 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (A+ — 100/100)

*No cookies set — no cookie security risks*

- **[PASS]** No cookies set — no cookie security risks

### Cookie Hygiene (A+ — 100/100)

*No cookies set -- cookie-hygiene check is N/A*

- **[PASS]** No cookies set

### WAF / Bot Protection (B — 75/100)

*No WAF detected via response headers*

- **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

### security.txt (A+ — 100/100)

*Vulnerability disclosure policy*

- **[PASS]** security.txt found
- **[PASS]** security.txt is PGP signed

### Cross-Origin Tab Safety (A+ — 100/100)

*All 3 new-tab link(s) carry rel=noopener*

- **[PASS]** All 3 new-tab link(s) carry rel=noopener

### CSP Inline-Style Readiness (C — 75/100)

*22 inline style attribute(s) detected*

- **[WARNING]** 22 inline style attribute(s) detected — Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 22 inline style(s) is moderate. Affected element types include: div, img, span, i, ul. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

### Trusted Types (XSS Sink Hardening) (B — 95/100)

*Trusted Types not enabled*

- **[INFO]** Trusted Types not enabled — Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

### Bot Challenge Detection (A+ — 100/100)

*Scan reached real page content (no bot-protection interstitial)*

- **[PASS]** No bot-protection interstitial detected -- the rest of the report reflects the real page

### Soft-404 Detection (A+ — 100/100)

*No soft-404 patterns detected in page title or headings*

- **[PASS]** No soft-404 patterns detected in page title or headings

### Empty Page Detection (A+ — 100/100)

*Page has substantive body text and no placeholder / template-leak signals*

- **[PASS]** Page has substantive body text and no placeholder / template-leak signals

### Geo-Restriction Detection (A+ — 100/100)

*No geo-restriction signals detected -- scan reached the page from an allowed region*

- **[PASS]** No geo-restriction detected

### Maintenance Mode Detection (A+ — 100/100)

*No maintenance-mode signals detected -- scan reached a normal page*

- **[PASS]** No maintenance-mode signals detected

### Subresource Integrity Adoption (F — 30/100)

*0% SRI adoption (0/7 third-party resources)*

- **[WARNING]** SRI adoption: 0/7 third-party resources protected (0%) — Of 7 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 5 examples):
  - https://kit.fontawesome.com/8442ade4bd.js
  - https://app.tolkie.nl/tolkie-client.min.css
  - https://cdn.tolkie.nl/website_css/4bfed61c-4ae3-4576-bc1e-4a119fefa17e.css
  - https://app.tolkie.nl/
  - https://scripts.simpleanalyticscdn.com/latest.js

Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

### CORS Depth (A+ — 100/100)

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

### Permissions-Policy Granularity (A — 85/100)

*90% high-risk feature coverage (9/10)*

- **[PASS]** Permissions-Policy covers 9/10 high-risk features (90%) — The Permissions-Policy header explicitly declares policies for 9/10 high-risk features.

Covered: camera, microphone, geolocation, payment, usb, midi, accelerometer, gyroscope, magnetometer

Not declared (default-allow): serial

The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

### Referrer-Policy Strictness (A+ — 100/100)

*Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)*

- **[PASS]** Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin — The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value.

### Source Map Exposure (A+ — 100/100)

*No source maps accessible (probed 1 candidate URL(s))*

- **[PASS]** No source maps accessible across 1 probed candidate(s)

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

### Auth Security (A+ — 100/100)

*Page is not a login form -- auth-security checks are N/A*

- **[PASS]** Page does not appear to be a login form

### Subdomain Inventory Exposure (B — 90/100)

*1 risky subdomain name(s) in certificate SANs*

- **[INFO]** 1 risky subdomain name(s) advertised in certificate SANs — These names are publicly visible via Certificate Transparency logs (crt.sh, censys.io) -- any attacker can enumerate them in seconds. Operators are often unaware that internal/staging/admin endpoints are inadvertently advertised this way. Mitigation: use a wildcard cert that doesn't enumerate, issue per-environment certs without non-prod SANs on the prod cert, or move internal services to private DNS off the public cert.

---

## Advanced Security

### Subresource Integrity (F — 20/100)

*0 of 7 external resources have SRI*

- **[WARNING]** External script from kit.fontawesome.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from app.tolkie.nl lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from cdn.tolkie.nl lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from app.tolkie.nl lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from scripts.simpleanalyticscdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from virtuele-gemeente-assistent.nl lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from virtuele-gemeente-assistent.nl lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

### JS Library Vulnerabilities (A+ — 100/100)

*No known vulnerabilities*

- **[PASS]** No known JavaScript library vulnerabilities detected

### Information Leakage (A+ — 100/100)

*No exposures*

- **[PASS]** security.txt is present — good practice
- **[PASS]** No sensitive files exposed

### Email Security (F — 0/100)

*no DMARC, no SPF*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

### API Surface (A+ — 100/100)

*No API specs or GraphQL introspection found (probed 11 candidate path(s))*

- **[PASS]** No API specs or GraphQL introspection found (probed 11 path(s))

### Permissions-Policy (C — 60/100)

*19 directives, 0 missing*

- **[INFO]** accelerometer=(self)
- **[INFO]** autoplay=(self)
- **[INFO]** camera=(self)
- **[INFO]** cross-origin-isolated=(self)
- **[INFO]** document-domain=*
- **[INFO]** encrypted-media=(self)
- **[INFO]** fullscreen=(self "https://www.youtube.com" "https://youtu.be" "https://player.vimeo.com" "https://www.vimeo.com")
- **[INFO]** geolocation=(self)
- **[INFO]** gyroscope=(self)
- **[INFO]** magnetometer=(self)
- **[INFO]** microphone=(self)
- **[INFO]** midi=(self)
- **[INFO]** payment=(self)
- **[INFO]** picture-in-picture=*
- **[INFO]** publickey-credentials-get=(self)
- **[INFO]** screen-wake-lock=(self)
- **[INFO]** sync-xhr=*
- **[INFO]** usb=(self)
- **[INFO]** xr-spatial-tracking=(self)

### CORS Configuration (B — 80/100)

*No CORS headers*

- **[PASS]** No CORS headers present — secure default

---

## Performance

### Page Weight Budget (F — 6/100)

*3.7 MB transferred, 75 requests*

- **[WARNING]** Page weighs 9.6 MB (3.7 MB transferred)
- **[WARNING]** JavaScript is 2.4 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** Fonts are 528 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[INFO]** 75 HTTP requests
- **[INFO]** Estimated 0.78 g CO2 per page load

### Third-Party Impact (D — 50/100)

*81% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 81% of page weight (3.0 MiB of 3.7 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

### Text Compression (A+ — 100/100)

*All text resources are compressed*

- **[PASS]** All text resources are compressed

### Image Optimization (C — 60/100)

*15 images, 0 KB saveable*

- **[WARNING]** https://openpub.pijnacker-nootdorp.nl/wp-content/u... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://openpub.pijnacker-nootdorp.nl/wp-content/u... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://openpub.pijnacker-nootdorp.nl/wp-content/u... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

### JS Execution Cost (D — 40/100)

*3438ms total JS execution*

- **[WARNING]** https://www.pijnacker-nootdorp.nl/: 1176ms CPU time
- **[WARNING]** https://virtuele-gemeente-assistent.nl/static/js/i...: 755ms CPU time
- **[WARNING]** Unattributable: 636ms CPU time
- **[WARNING]** https://www.pijnacker-nootdorp.nl/wp-content/theme...: 261ms CPU time
- **[INFO]** https://app.tolkie.nl/: 228ms CPU time
- **[INFO]** Third-party scripts: 983ms (29% of total)

### Font Loading (A+ — 100/100)

*23 fonts (528 KB)*

- **[INFO]** 23 font(s) use font-display: swap (FOUT risk but functional)

### JS Bundles (D — 40/100)

*15 scripts, 467 KB unused*

- **[WARNING]** https://virtuele-gemeente-assistent.nl/static/js/i...: 377 KB unused (22%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.pijnacker-nootdorp.nl/wp-content/theme...: 89 KB unused (57%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 467 KB

### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A+ — 100/100)

*2 hints, 0 missing preconnects*

- **[PASS]** Page uses 2 resource hint(s)

### HTTP/3 (QUIC) (B — 75/100)

*HTTP/3 not advertised*

- **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

### Document Compression (A+ — 100/100)

*Document response uses brotli*

- **[PASS]** Main HTML response uses brotli (Content-Encoding: br) — Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it.

### Asset Compression (A+ — 100/100)

*All 1 asset host use brotli*

- **[PASS]** app.tolkie.nl serves assets with brotli (assets: 3)

### LCP Image Preload (A+ — 100/100)

*LCP preload audit not available*

- **[PASS]** LCP image preload audit not available for this scan

### Main HTML Cache-Control (B — 80/100)

*No Cache-Control header on main HTML response*

- **[INFO]** Main HTML response has no Cache-Control header — Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.

### Server-Timing Observability (B — 85/100)

*No Server-Timing header found*

- **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

### Server Response Intelligence (A — 87/100)

*2 server-response signal(s) detected*

- **[WARNING]** Compressed response missing `Vary` header — The page is served with `Content-Encoding: br` but has no `Vary` header. Without `Vary: Accept-Encoding`, intermediary caches (corporate proxies, ISP caches) may serve the compressed variant to clients that didn't send the matching `Accept-Encoding` -- the client sees garbled bytes. Add `Vary: Accept-Encoding` whenever the response is conditionally compressed.
- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

### Page Weight Inventory (F — 35/100)

*75 resources · 3.7 MB · 467 KB savings available*

- **[WARNING]** Page weight 3.7 MB exceeds 1 MB target by 2.7 MB
- **[INFO]** ~467 KB of savings available
- **[WARNING]** 51 third-party resources (81% of weight)
- **[INFO]** 3 resources over 200KB

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

### Third-Party Resources (A+ — 100/100)

*No third-party resources detected*


### JavaScript Blocking (A — 94/100)

*1 JS blocking issue(s) detected*

- **[WARNING]** 1 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.

### CSS Performance Depth (A — 88/100)

*1 CSS depth issue(s) detected*

- **[WARNING]** 6 render-blocking stylesheet(s) -- recommended: <=3 — Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.

---

## Content Quality

### Links (F — 40/100)

*94 links checked, 41 healthy, 53 broken*

- **[CRITICAL]** 41 of 94 links are healthy
- **[WARNING]** Broken link: https://www.pijnacker-nootdorp.nl/manifest.webmanifest — Found in <link href>. Returns HTTP 404.
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/privacyverklaring — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/privacyverklaring": context deadline exceeded
- **[WARNING]** Broken link: https://www.pijnacker-nootdorp.nl/wp-content/plugins/cook... — Found in <img src>. Get "https://www.pijnacker-nootdorp.nl/wp-content/plugins/cookie-law-info/lite/frontend/images/close.svg": context deadline exceeded
- **[WARNING]** Broken link: https://www.pijnacker-nootdorp.nl/wp-content/uploads/2020... — Found in <img src>. Get "https://www.pijnacker-nootdorp.nl/wp-content/uploads/2020/02/cropped-pijnacker_logo.png": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/belastin... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/belastingen-en-woz": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-e... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-en-wonen": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/levensge... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/levensgebeurtenissen": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/melding-... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/melding-of-klacht": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/ondernemen — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/ondernemen": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/onderwijs — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/onderwijs": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/reisdocu... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/reisdocumenten-uittreksels-en-verklaringen": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/sport-cu... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/sport-cultuur-en-recreatie": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/verkeer-... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/verkeer-vervoer-parkeren": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/werken-i... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/werken-inkomen-en-schulden": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/zorg-en-... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/zorg-en-welzijn": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/actueel/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/actueel/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/economische-conferentie... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/economische-conferentie-2026/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/bekendmakingen/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/bekendmakingen/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/informatiepagina-oekraine/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/informatiepagina-oekraine/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/plannen-ter-inzage/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/plannen-ter-inzage/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/projecten/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/projecten/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/politiek-en-organisatie/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/politiek-en-organisatie/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/contact/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/contact/": context deadline exceeded
- **[WARNING]** Broken link: https://www.pijnacker-nootdorp.nl/wp-content/uploads/2026... — Found in <img src>. Get "https://www.pijnacker-nootdorp.nl/wp-content/uploads/2026/09/Herfst2026def-scaled.jpg": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-e... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-en-wonen/afval-inzamelen/3748/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-e... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-en-wonen/melding-doorgeven/2137": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/reisdocu... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/reisdocumenten-uittreksels-en-verklaringen/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/reisdocu... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/reisdocumenten-uittreksels-en-verklaringen/rijbewijs-aanvragen-of-verlengen/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-e... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-en-wonen/verhuizing-doorgeven/319/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/ondernemen/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/ondernemen/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/verkeer-... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/verkeer-vervoer-parkeren/gladheidbestrijding/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/belastin... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/belastingen-en-woz/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-e... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/direct-regelen/bouwen-en-wonen/aan-de-slag-met-duurzaamheid/": context deadline exceeded
- **[WARNING]** Broken link: https://openpub.pijnacker-nootdorp.nl/wp-content/uploads/... — Found in <img src>. Get "https://openpub.pijnacker-nootdorp.nl/wp-content/uploads/2020/09/Gemeentekantoor.jpg": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/actueel/pijnacker-nootd... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/actueel/pijnacker-nootdorp-maakt-afspraken-over-opvang-en-huisvesting-in-de-regio/29422/": context deadline exceeded
- **[WARNING]** Broken link: https://openpub.pijnacker-nootdorp.nl/wp-content/uploads/... — Found in <img src>. Get "https://openpub.pijnacker-nootdorp.nl/wp-content/uploads/2026/10/ANP-571766320-768x512.jpg": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/actueel/kom-demi-voller... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/actueel/kom-demi-vollering-toejuichen-langs-de-ereroute-op-vrijdag-20-november/29414/": context deadline exceeded
- **[WARNING]** Broken link: https://openpub.pijnacker-nootdorp.nl/wp-content/uploads/... — Found in <img src>. Get "https://openpub.pijnacker-nootdorp.nl/wp-content/uploads/2026/11/3GN4918-768x512.jpg": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/actueel/imany-is-onze-n... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/actueel/imany-is-onze-nieuwe-kinderburgemeester/29391/": context deadline exceeded
- **[WARNING]** Broken link: https://www.pijnacker-nootdorp.nl/wp-content/uploads/2024... — Found in <img src>. Get "https://www.pijnacker-nootdorp.nl/wp-content/uploads/2024/04/Participatie-home.png": context deadline exceeded
- **[WARNING]** Broken link: https://www.pijnacker-nootdorp.nl/wp-content/uploads/2022... — Found in <img src>. Get "https://www.pijnacker-nootdorp.nl/wp-content/uploads/2022/09/0001931.jpg": context deadline exceeded
- **[WARNING]** Broken link: https://www.pijnacker-nootdorp.nl/wp-content/uploads/2020... — Found in <img src>. Get "https://www.pijnacker-nootdorp.nl/wp-content/uploads/2020/06/NPN-homepage-image-1024x538.png": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.natuurlijkpn.nl — Found in <a href>. Get "https://www.natuurlijkpn.nl": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/contact/aanmelden-nieuw... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/contact/aanmelden-nieuwsbrief": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/contact/whatsapp/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/contact/whatsapp/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/home/bekendmakingen/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/home/bekendmakingen/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/lokale-wet-en-regelgeving/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/lokale-wet-en-regelgeving/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/wet-open-overheid/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/wet-open-overheid/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/politiek-en-organisatie... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/politiek-en-organisatie/vacatures/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/toegankelijkheidsverkla... — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/toegankelijkheidsverklaring/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/privacyverklaring/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/privacyverklaring/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/proclaimer/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/proclaimer/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.pijnacker-nootdorp.nl/home/archief-website/ — Found in <a href>. Get "https://www.pijnacker-nootdorp.nl/home/archief-website/": context deadline exceeded

### Mixed Content (B — 80/100)

*1 HTTP resource(s) loaded on HTTPS page*

- **[CRITICAL]** HTTP link loaded on HTTPS page — Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.

### Open Graph (B — 85/100)

*Open Graph tags are partially configured — some improvements recommended.*

- **[WARNING]** Missing og:description — The og:description tag controls the description in social sharing previews.

### Open Graph / Twitter Card Depth (A — 90/100)

*1 OG/Twitter depth issue(s) detected*

- **[INFO]** og:image aspect ratio 1.00:1 (512×512) is outside Facebook's recommended ~1.91:1 — Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 512×512 give a ratio of 1.00:1, which Facebook will crop center-to-fit; the result often clips important content from the top/bottom or sides. Use a wider/taller image close to 1.91:1, or accept the cropping consequences.

### Structured Data (A+ — 100/100)

*1 JSON-LD block(s) found — structured data is well configured.*

- **[INFO]** Missing recommended property "potentialAction" for WebSite — Adding "potentialAction" can improve how search engines display your content.

### Rich Results Eligibility (A+ — 100/100)

*1 JSON-LD block(s) declaring 1 schema type(s)*

- **[PASS]** 1 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

WebSite

Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.

### Image Optimization (D — 60/100)

*4 issues found across 15 images*

- **[WARNING]** 10 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 12 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 8 images use legacy formats (JPEG/PNG/GIF) — WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
- **[INFO]** 6 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://www.pijnacker-nootdorp.nl/wp-content/uploads/2026/09/Herfst2026def-1024x624.jpg, https://openpub.pijnacker-nootdorp.nl/wp-content/uploads/2020/09/Gemeentekantoor-300x200.jpg, https://openpub.pijnacker-nootdorp.nl/wp-content/uploads/2026/10/ANP-571766320-300x200.jpg (+3 more).

### Autoplay Media (A+ — 100/100)

*No autoplay media on the page*

- **[PASS]** No autoplay media on the page

---

## Infrastructure

### DNS Records (A — 90/100)

*3 A records, 52 ms lookup*

- **[PASS]** Resolves to 3 IPv4 address(es)
- **[PASS]** Has 3 IPv6 (AAAA) record(s)
- **[INFO]** No NS records found
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[PASS]** DNS resolution time: 52 ms

### Subdomain Takeover (A+ — 100/100)

*No subdomain takeover risk detected*

- **[PASS]** No CNAME record present

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

### CAA Records (B — 80/100)

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

### Reverse DNS (B — 75/100)

*0/6 IPs match cert SAN*

- **[INFO]** PTR for 31.7.6.87 does not match any cert SAN: customer-lb2.k8s.shockmedia.host — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 31.7.0.60 does not match any cert SAN: customer-lb1.k8s.shockmedia.host — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 185.144.224.28 does not match any cert SAN: customer-lb3.k8s.shockmedia.host — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 2a03:9700:8000:1::24 does not match any cert SAN: customer-lb2.k8s.shockmedia.host — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 2a03:9700:8000:1::23 does not match any cert SAN: customer-lb1.k8s.shockmedia.host — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 2a03:9700:8000:1::25 does not match any cert SAN: customer-lb3.k8s.shockmedia.host — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

### Multi-Resolver DNS Speed (A — 90/100)

*Mean 53ms across 3 resolvers (spread 58ms)*

- **[PASS]** Google: 26ms
- **[PASS]** Cloudflare: 51ms
- **[PASS]** Quad9: 84ms

### Redirect Chain (A+ — 100/100)

*No redirects — direct access*

- **[PASS]** No redirects — direct access

### IPv6 Readiness (A+ — 100/100)

*IPv6 reachable (28 ms)*

- **[PASS]** IPv6 is configured and reachable at 2a03:9700:8000:1::24, 2a03:9700:8000:1::23, 2a03:9700:8000:1::25

### Crawlability (A+ — 95/100)

*robots.txt present, sitemap with 6 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 6 entries
- **[PASS]** Sitemap index with 6 child sitemaps
- **[INFO]** robots.txt does not reference a sitemap — Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

### URL Variants (A+ — 100/100)

*www/non-www, trailing slash, HTTP→HTTPS*

- **[PASS]** HTTP correctly redirects to HTTPS permanently

### Domain Intelligence (A+ — 100/100)

*pijnacker-nootdorp.nl — via KPN B.V., 25 years, 9 months old*

- **[PASS]** DNSSEC is enabled
- **[PASS]** Registrar: KPN B.V.
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## Compliance

### WCAG Compliance (A+ — 100/100)

*No testable criteria*


### Cookie Consent & Privacy (A+ — 95/100)

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

### Consent UX Depth (A+ — 100/100)

*No consent-UX depth issues detected*

- **[PASS]** No consent-UX depth issues detected

### Tracker Inventory (A+ — 100/100)

*No known trackers detected on this page*

- **[PASS]** No known trackers detected on this page

### Language & i18n (A — 90/100)

*Lang attribute present*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[INFO]** No Content-Language HTTP header
- **[INFO]** Language signals are inconsistent — The <html lang> attribute and Content-Language header should agree.

### Hreflang Configuration (A+ — 100/100)

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

### Internationalization Extras (A+ — 100/100)

*No additional i18n signals detected*

- **[PASS]** No additional i18n signals detected

### Readability & Typography (A+ — 100/100)

*Font sizes and tap targets checked*


### Viewport Configuration (A+ — 100/100)

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[PASS]** User zooming is allowed

### Accessibility Statement (B — 70/100)

*No accessibility statement detected*

- **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence.

### GDPR Article 13 Disclosures (D — 50/100)

*0 / 8 Art. 13 categories matched in homepage body*

- **[INFO]** GDPR Article 13 disclosures not assessed (policy language: nl-NL) — The privacy policy appears to be written in "nl-NL", which this check has no disclosure patterns for (currently English, French, German and Spanish). No conclusion is drawn about the policy's completeness, and this finding is excluded from the regulatory-risk estimate.

### Third-Party Trackers (A+ — 95/100)

*2 trackers detected*

- **[INFO]** 2 third-party trackers detected — Found 2 analytics, 0 advertising, 0 marketing, 0 tag manager, 0 session-replay, 0 heatmap trackers.

### Cookie & Tracker Inventory (A+ — 100/100)

*0 cookies · 2 trackers · 0 pre-consent*

- **[INFO]** 2 third-party tracker(s) detected on page

### Tracking Pixel Inventory (A+ — 100/100)

*No tracking pixels detected*

- **[PASS]** No tracking pixels detected

### Browser Fingerprinting (A+ — 100/100)

*No browser-fingerprinting libraries detected*

- **[PASS]** No browser-fingerprinting libraries detected

### Cross-Site Cookies (SameSite=None) (A+ — 100/100)

*No cookies on the page*

- **[PASS]** No cookies set on the page response

### Beacon Tracking (sendBeacon) (A+ — 100/100)

*No navigator.sendBeacon usage detected in inline scripts*

- **[PASS]** No navigator.sendBeacon usage detected in inline scripts

---

## Legal

### Legal Page Ecosystem (F — 30/100)

*1 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /privacyverklaring.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (C — 55/100)

*No copyright notice detected*

- **[INFO]** No copyright notice detected — No copyright notice detected in the page content. While not legally required in most jurisdictions (copyright exists automatically), a notice is standard practice and signals site ownership.

### Regulatory Indicators

*1 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** GDPR indicators detected (strong confidence) — Indicators suggesting GDPR may be relevant: European TLD detected: .nl; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### Third-Party Data Sharing

*0 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** No recognized third-party data-sharing services detected — This page does not appear to load external tracking, analytics, or advertising scripts.

### Compliance Badges (C — 55/100)

*0 compliance badge(s) detected*

- **[INFO]** No compliance badges detected — No recognized compliance certification badges or seals were found. This is common — many sites do not display compliance badges.

---

## Availability

### CDN & Delivery (C — 65/100)

*Assets on AWS CloudFront (host app.tolkie.nl, 3 assets); document served directly from origin*

- **[WARNING]** Document not behind existing CDN (AWS CloudFront serves the assets) — The page's subresources are delivered by AWS CloudFront (app.tolkie.nl, 3 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
- **[PASS]** Assets on AWS CloudFront: app.tolkie.nl (assets: 3), cache Hit from cloudfront

### HTTP Caching (F — 30/100)

*No cache headers*

- **[WARNING]** No Cache-Control header found — Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (A — 90/100)

*HTTP/3, HSTS, and TLS version analysis*

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[PASS]** HSTS enabled (includeSubDomains)
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (B — 80/100)

*No conventional health endpoint found*

- **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: 404, /healthz: connection error, /ping: connection error, /status: connection error.

### CDN Cache Observability (B — 85/100)

*No CDN cache-status headers in the response*

- **[INFO]** No CDN cache-status headers in the response — Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

---

## Accessibility

### Landmark Structure (B — 70/100)

*4 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 2 <nav> landmark(s) found
- **[WARNING]** 1 of 2 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[INFO]** No banner (header) landmark
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

### Heading Hierarchy (A+ — 100/100)

*24 headings*

- **[PASS]** Single H1 present

### Heading Text Quality (A+ — 100/100)

*All 24 heading(s) have substantive, well-formed text*

- **[PASS]** Heading text quality is clean -- no placeholder, length, or styling issues

### Alt Text Quality (A+ — 100/100)

*All 15 images OK*

- **[PASS]** 13 decorative image(s) correctly marked
- **[PASS]** 2 image(s) with good alt text

### Form Accessibility (A+ — 100/100)

*All 4 controls labeled*

- **[PASS]** 4 control(s) properly labeled

### Link & Button Quality (A — 88/100)

*69 links, 27 buttons — all OK*

- **[WARNING]** 5 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 64 link(s) with descriptive text

### Form Input Types (A+ — 100/100)

*4 form control(s) checked, no type mismatches*

- **[PASS]** No input-type mismatches detected

### Form Input Quality (A+ — 100/100)

*4 form control(s) checked, no input-semantic issues*

- **[PASS]** All form input semantics look correct

### Mobile Keyboard & Autofill (A+ — 100/100)

*No autofill-eligible form controls*

- **[PASS]** No autofill-eligible form controls (no name/email/tel/address fields)

### Document Language (A+ — 100/100)

*Lang attribute set to "nl-NL"*

- **[PASS]** <html lang="nl-NL"> is set and valid

### Tabindex Anti-Patterns (A — 90/100)

*0 positive, 2 -1-on-focusable*

- **[INFO]** tabindex="-1" on naturally-focusable <button id="tolkie-separate-summary"> — tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

### Iframe Accessibility (A+ — 100/100)

*All 1 iframe(s) have descriptive titles*

- **[PASS]** All 1 iframe(s) have title attributes

### Tap Target Adequacy (A+ — 100/100)

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

- **[PASS]** All tap targets meet WCAG 2.5.5 (44x44px) sizing

### Mobile-Readable Font Sizes (B — 90/100)

*98% of visible text renders at >= 12 CSS px (1 below threshold)*

- **[INFO]** 1 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Vertalen").

---

## UX

### 404 Error Page (C — 55/100)

*Could not test*

- **[INFO]** 404 page could not be tested — The 404 page check encountered an error. This may be due to a timeout or network issue.

### Favicon & Branding (C — 55/100)

*3 icon(s) detected*

- **[WARNING]** No favicon.ico at site root — Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

### Web Manifest (D — 40/100)

*Not found*

- **[INFO]** No web manifest found — No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

### PWA Depth (A+ — 100/100)

*No PWA depth issues detected*

- **[PASS]** No PWA depth issues detected

### Dark Mode Support (D — 45/100)

*Theme color only*

- **[INFO]** Theme-color present but no dark variant — A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

### Print Stylesheet (D — 40/100)

*No print styles*

- **[INFO]** No print-specific styles detected — When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

### Navigation UX (F — 20/100)

*No navigation patterns*

- **[PASS]** 2 navigation landmark(s) detected
- **[PASS]** Hamburger menu detected (responsive design)
- **[INFO]** No breadcrumbs, search, or skip link detected — These navigation aids help users orient themselves and find content efficiently, especially on large sites.

### Mobile UX Depth (A+ — 100/100)

*1 mobile-depth signal(s) detected*

- **[PASS]** Browser-chrome `theme-color` meta tag present — The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

---

## SEO

### Canonical URL (A+ — 100/100)

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target reachable (self-referencing)

### Meta Tags (A — 85/100)

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (34 chars) is optimal
- **[WARNING]** No meta description tag found — Without a meta description, Google auto-generates a snippet from page content -- usually less click-attractive than a hand-written summary. Add `<meta name="description" content="...">` with a 70-160 char summary.
- **[PASS]** Title and H1 are well-aligned

### Title Style Depth (A — 90/100)

*1 title-style issue(s) detected*

- **[INFO]** Title uses 2 different separator characters: |, - — The page title `Home | Gemeente Pijnacker-Nootdorp` uses multiple separator characters (|, -). Consistent separator use is a soft signal of careful editorial control; mixed separators usually mean the title was assembled from multiple template fragments (CMS title + brand + section) without a normalization step. Pick one separator (commonly `|`, `-`, or `:`) and stick with it across the whole site.

### Content Depth (A — 85/100)

*1297 words, Very Difficult*

- **[PASS]** Page has 1297 words — good depth for search engines
- **[INFO]** Text-to-HTML ratio is 1% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Very Difficult (grade 16)

### Internal Links (A+ — 100/100)

*53 internal, 16 external*

- **[PASS]** 53 internal links (77%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 53 internal / 16 external links

### Image SEO (A+ — 100/100)

*15 images, 14 descriptive filenames*

- **[INFO]** 1 image(s) have hash/generic filenames

### Hreflang

*0 hreflang tags*


### Hreflang URL Quality (A+ — 100/100)

*No hreflang tags on the page*

- **[PASS]** No hreflang tags on the page

### Hreflang Completeness (A+ — 100/100)

*No hreflang tags on this page -- check is N/A (single-language site or unannotated)*

- **[PASS]** No hreflang tags found -- completeness check is N/A

### Sitemap Freshness (A+ — 100/100)

*Sitemap updated within 90 days (3/6 URLs have lastmod)*

- **[PASS]** Sitemap actively maintained — newest lastmod: 2 days ago

### Sitemap × Robots Consistency (A+ — 100/100)

*No sitemap-vs-robots conflicts detected*

- **[PASS]** Sitemap URLs are not blocked by robots.txt

### Sitemap Hygiene (A+ — 100/100)

*Sitemap structure / size look healthy (6 URLs, 1 KB)*

- **[PASS]** Sitemap structure / size look healthy (6 URLs)

### Markup Quality (A+ — 100/100)

*No markup-quality issues detected*

- **[PASS]** No markup-quality issues detected

---

## Sustainability

### CO2 Per Page Load (D — 50/100)

*0.88g CO2 per view*

- **[INFO]** 0.88g CO2 per page view — This page transfers 3.7 MB, producing an estimated 0.88g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.02g, network 0.18g, end-user device 0.67g.
- **[INFO]** At 10,000 monthly views: 105.2 kg CO2/year — With 10,000 page views per month, this page would generate approximately 105.2 kg of CO2 annually — equivalent to charging 13152 smartphones.
- **[PASS]** Green hosting reduces data center emissions

### Green Hosting (B — 80/100)

*Green (hosting)*

- **[PASS]** Amazon Web Services uses renewable energy
- **[INFO]** Amazon Web Services: Verified by the Green Web Foundation
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

### Repeat Visit Weight (A+ — 100/100)

*99% cached*

- **[PASS]** 99% reduction on repeat visits — Returning visitors download only 22 KB (vs 3793 KB first visit). 73 of 75 resources are served from browser cache, saving 0.87g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.88g)

### Carbon Budget (D — 50/100)

*57th percentile*

- **[WARNING]** 0.88g CO2 — above the median website (0.60g) — Heavier than an estimated 43% of websites. Reducing page weight, optimizing images, and removing unused JavaScript would lower the carbon footprint. See the Performance tab.
- **[INFO]** Estimated 57th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (B — 80/100)

*88% efficient*

- **[INFO]** Transfer efficiency: 88% — An estimated 466 KB (12%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 466 KB of unused JavaScript. This wasted data produces 0.11g of unnecessary CO2 per page view.

### Web Font Weight Variants (B — 90/100)

*No detectable Google Fonts weights*

- **[INFO]** No detectable Google Fonts weights — The analyzer detects font weights via Google Fonts URL parameters (~70% of font-using sites). Self-hosted fonts and non-Google CDN fonts aren't visible to URL-based detection. If you self-host fonts, manually audit how many @font-face weights you ship -- 2-3 weights per family is typically enough; 5+ is usually unused payload.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/7f311269-1a0a-4c70-96f3-6e7131d3f113*