Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.06 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.53 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
98 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.152
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.24 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.83 s
Page Load Progression
375 ms
750 ms
1.1 s
1.5 s
1.9 s
2.2 s
2.6 s
3.0 s
Checks
24
9 PASS7 REVIEW4 FIX
F
Page Weight Budget
Action
3.3 MB transferred, 134 requests
FIX
3.3 MB transferred, 134 requests
Warning::
!
Page weighs 11.2 MB (3.3 MB transferred)
Warning::
!
JavaScript is 1.1 MB — consider code splitting or lazy loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Got: 1.1 MB
Warning::
!
Images are 1.1 MB — compress or use modern formats
Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
Got: 1.1 MB
Info::
i
Fonts are 416 KB — consider subsetting or using system fonts
Subset fonts to include only used characters, or switch to system font stacks.
Got: 416 KB
Warning::
!
134 HTTP requests — consider bundling or reducing
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
Info::
i
Estimated 0.69 g CO2 per page load
3.3 MBtransferred
134 requests
0.69 g CO2 per page load
JavaScript1.1 MiB33%
Images1.1 MiB33%
Other536.4 KiB16%
Fonts415.5 KiB12%
CSS148.7 KiB4%
HTML48.7 KiB1%
Other2.5 KiB0%
Other1.5 KiB0%
Other103 B0%
Other0 B0%
Other0 B0%
02.4 MB4.9 MB
Over budget
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Why this matters
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
Why this matters
Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.
Source: web.dev
Subset fonts to include only used characters, or switch to system font stacks.
Why this matters
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
Why this matters
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Source: web.dev
D
Third-Party Impact
Action
88% third-party, 0 ms blocking
FIX
88% third-party, 0 ms blocking
Warning::
!
Third-party code accounts for 88% of page weight (2.9 MiB of 3.3 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
88%
First-party Third-party
D
Asset Compression
Action
1 of 4 asset hosts serve text uncompressed
FIX
1 of 4 asset hosts serve text uncompressed
Info::
i
cuatro.sim-cdn.nl serves assets with gzip; brotli would be ~20% smaller (assets: 79)
Every current browser accepts brotli. On a CDN this is a per-pull-zone toggle (Cloudflare, Fastly, CloudFront, CDN77, Bunny all expose it); on an origin it needs the brotli module (nginx-brotli, Apache mod_brotli). The saving lands on the assets this host serves, not on the HTML document -- the document's own encoding is reported separately.
Got: cuatro.sim-cdn.nl (text/css)
Info::
i
app.tolkie.nl serves assets with gzip; brotli would be ~20% smaller (assets: 3)
Every current browser accepts brotli. On a CDN this is a per-pull-zone toggle (Cloudflare, Fastly, CloudFront, CDN77, Bunny all expose it); on an origin it needs the brotli module (nginx-brotli, Apache mod_brotli). The saving lands on the assets this host serves, not on the HTML document -- the document's own encoding is reported separately.
Got: app.tolkie.nl (text/css)
Info::
i
cdn-eu.readspeaker.com serves assets with gzip; brotli would be ~20% smaller (assets: 3)
Every current browser accepts brotli. On a CDN this is a per-pull-zone toggle (Cloudflare, Fastly, CloudFront, CDN77, Bunny all expose it); on an origin it needs the brotli module (nginx-brotli, Apache mod_brotli). The saving lands on the assets this host serves, not on the HTML document -- the document's own encoding is reported separately.
Got: cdn-eu.readspeaker.com (text/css)
Warning::
!
woensdrecht.logging.simanalytics.nl serves text assets uncompressed (assets: 3)
The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
B
HTTP/3 (QUIC)
HTTP/3 not advertised
REVIEW
HTTP/3 not advertised
Info::
i
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.
B
Document Compression
Document response uses gzip; brotli would be ~20% smaller
REVIEW
Document response uses gzip; brotli would be ~20% smaller
Info::
i
Main HTML response uses gzip (brotli would be ~20% smaller)
All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.
B
Server-Timing Observability
No Server-Timing header found
REVIEW
No Server-Timing header found
Info::
i
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.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
✓
All text resources are compressed
All text resources are properly compressed.
A+
Font Loading
10 fonts (416 KB)
PASS
10 fonts (416 KB)
Info::
i
10 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
10
416 KB total
Render-blocking
0
of 10
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
open-sans-latin-400-nor...woff2swap
Size19 KB
Load time124 ms
Start368 ms
RiskFOUT — text flashes from fallback to web font
fa-solid-900.woff2woff2swap
Size155 KB
Load time154 ms
Start368 ms
RiskFOUT — text flashes from fallback to web font
Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
open-sans-latin-800-nor...woff2swap
Size19 KB
Load time135 ms
Start369 ms
RiskFOUT — text flashes from fallback to web font
open-sans-latin-300-nor...woff2swap
Size19 KB
Load time55 ms
Start457 ms
RiskFOUT — text flashes from fallback to web font
OpenGemeenten.woff2woff2swap
Size26 KB
Load time67 ms
Start458 ms
RiskFOUT — text flashes from fallback to web font
toptaken01.woff2woff2swap
Size10 KB
Load time69 ms
Start458 ms
RiskFOUT — text flashes from fallback to web font
fa-brands-400.woff2woff2swap
Size116 KB
Load time84 ms
Start458 ms
RiskFOUT — text flashes from fallback to web font
Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
x-font-ttf;charset=utf-...unknownswap
Size13 KB
Load time18 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
font-woff;charset=utf-8...woffswap
Size25 KB
Load time19 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
Convert to woff2 for ~30% smaller file size
atkinson-hyperlegible-n...woff2swap
Size13 KB
Load time28 ms
Start1.8 s
RiskFOUT — text flashes from fallback to web font
Optimization checklist
Preload critical fonts (priority=high)
Use woff2 format for all fonts
Set font-display to swap, optional, or fallback
Subset large fonts (≤100 KB each)
Fixing the unchecked items could save ~147 KB and ~294 ms
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
✓
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
✓
No render-blocking resources detected
A+
Resource Hints
No optimization needed
PASS
No optimization needed
Info::
✓
No resource hint issues
A+
LCP Image Preload
LCP preload audit not available
PASS
LCP preload audit not available
Info::
✓
LCP image preload audit not available for this scan
The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
Per-script blocking time, transfer cost, and cache headers
INFO
56%of JavaScript execution is third-party
First-party Third-party509ms · 399KB · €6/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
cuatro.sim-cdn.nl
cuatro.sim-cdn.nl
Other
209ms
62 KB
35%
€2/mo
Costly
woensdrecht.logging.simanalytics.nl
woensdrecht.logging.simanalytics.nl
Other
97ms
133 KB
44%
€1/mo
Optional
cuatro.sim-cdn.nl
cuatro.sim-cdn.nl
Other
80ms
5 KB
—
€1/mo
Optional
cuatro.sim-cdn.nl
cuatro.sim-cdn.nl
Other
67ms
5 KB
—
€1/mo
Optional
app.tolkie.nl
app.tolkie.nl
Other
56ms
195 KB
12%
€1/mo
Optional
cuatro.sim-cdn.nl
Other
Costly
Execution209ms
Transfer62 KB
Unused35%
Monthly Cost€2/mo
woensdrecht.logging.simanalytics.nl
Other
Optional
Execution97ms
Transfer133 KB
Unused44%
Monthly Cost€1/mo
cuatro.sim-cdn.nl
Other
Optional
Execution80ms
Transfer5 KB
Monthly Cost€1/mo
cuatro.sim-cdn.nl
Other
Optional
Execution67ms
Transfer5 KB
Monthly Cost€1/mo
app.tolkie.nl
Other
Optional
Execution56ms
Transfer195 KB
Unused12%
Monthly Cost€1/mo
These scripts may cost more than they're worth
cuatro.sim-cdn.nl adds 209ms and costs ~€2/month
56% of JavaScript execution time comes from third-party scripts.
Why this matters
Third-party scripts (analytics, ads, social, A/B testing) often dominate execution time — every one is a perf-and-privacy tax.
Learn more ▾▴
Each third-party script is a black box: you don't control when it loads, what it executes, or how much it grows. They often account for a major share of total blocking time on average sites (HTTP Archive's Web Almanac documents the trend). Audit which ones you actually need, defer the rest, and use facade patterns (lite-youtube, lite-vimeo) for embedded media.
Source: web.dev / HTTP Archive Web Almanac
cuatro.sim-cdn.nl takes 209ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.