Skip to content
https://edp.org

Performance

· 27 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
94
GRADE
A
FIX
1
REVIEW
6
PASS
16
INFO
4

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

Mobile Desktop
100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
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.

782 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

782 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

782 ms

Page Load Progression

479 ms
957 ms
1.4 s
1.9 s
2.4 s
2.9 s
3.4 s
3.8 s
Checks
27
16 PASS 6 REVIEW 1 FIX
F
HTTP Caching
Action
No cache headers
FIX
No cache headers
Warning::
No Cache-Control header found
Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.
Info::
Last-Modified header present

No Cache-Control header

Adding a Cache-Control header can significantly improve repeat-visit performance.

B
HTTP/3 (QUIC)
HTTP/3 not advertised
REVIEW
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.
C
Compression Algorithm
Action
Main response served uncompressed
REVIEW
Main response served uncompressed
Info::
Main HTML response has no Content-Encoding (uncompressed)
The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.
B
Main HTML Cache-Control
No Cache-Control header on main HTML response
REVIEW
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.
B
Server-Timing Observability
No Server-Timing header found
REVIEW
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.
B
JavaScript Blocking
2 JS blocking issue(s) detected
REVIEW
2 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.
Warning::
Page uses document.write() -- disables Chrome's preload scanner
`document.write()` blocks all parallel resource discovery while it executes. Chrome explicitly disables the preload scanner on connections it judges slow when document.write is detected, serializing the entire subtree load. Almost always third-party ad / analytics legacy code; replacing with createElement + appendChild (or refusing to integrate the offending vendor) recovers significant load-time on mobile.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW

Green Hosting

No green hosting detected

A+
Page Weight Budget
11 KB transferred, 5 requests
PASS
11 KB transferred, 5 requests
Info::
Page weighs 11 KB (11 KB transferred)
Info::
5 HTTP requests
Info::
Estimated 0.00 g CO2 per page load
11 KB / 2.4 MB budget
11 KB transferred
5 requests
0.00 g CO2 per page load
HTML 4.4 KiB 40%
JavaScript 3.9 KiB 34%
Images 1.4 KiB 12%
Other 1.1 KiB 10%
CSS 397 B 3%
0 2.4 MB 4.9 MB
Under budget
A+
Third-Party Impact
No third-party resources
PASS
No third-party resources
Info::
No third-party resources detected
No third-party resources detected — all resources are first-party.
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
Image Optimization
1 images, 0 KB saveable
PASS
1 images, 0 KB saveable
Warning::
https://edp.org/Image/vim.vialle.love.gif is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
1 images 1 KB
0 oversized -0 KB
1 legacy format
1 missing dimensions CLS risk

Set explicit width and height to prevent CLS.

Why this matters

Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.

Source: web.dev / Core Web Vitals

A+
JS Execution Cost
143ms total JS execution
PASS
143ms total JS execution
Info::
https://edp.org/: 74ms CPU time
Info::
Unattributable: 70ms CPU time
Info::
Third-party scripts: 70ms (49% of total)

Main Thread Breakdown

Other 49% Style & Layout 31% Script Evaluation 10% Parse HTML & CSS 5% Rendering 3%
ScriptTotalScriptingParse/CompileParty
https://edp.org/74ms7ms2ms1st
Unattributable70ms5ms0ms3rd
A+
Font Loading
No web fonts (system fonts)
PASS
No web fonts (system fonts)
Info::
No web fonts loaded — system fonts are fastest
No web fonts loaded — system fonts are optimal.
A+
JS Bundles
1 scripts, 0 KB unused
PASS
1 scripts, 0 KB unused
0 KB unused JavaScript

Downloaded but never executed on this page.

ScriptSizeUnusedMinifiedParty
https://edp.org/edp.js4 KB—✓1st
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
A+
Server Response Intelligence
1 server-response signal(s) detected
PASS
1 server-response signal(s) detected
Info::
`Last-Modified` present -- timestamp-based conditional GET supported
Consider also setting `ETag` for stronger revalidation -- ETags are content hashes that don't suffer from clock-skew or DST issues. Last-Modified alone is functional for conditional GETs and not a bug.
A+
Page Weight Inventory
5 resources · 11 KB · 0 KB savings available
PASS
5 resources · 11 KB · 0 KB savings available
Info::
Within 1MB page-weight target
Got: 11 KB
5 resources · 11.2 KiB · 0 third-party Within 1MB page-weight target
Document 40% · 4.4 KiB
JavaScript 34% · 3.9 KiB
Image 23% · 2.5 KiB
CSS 3% · 397 B
A+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
A+
CSS Performance Depth
No CSS performance depth issues detected
PASS
No CSS performance depth issues detected
Info::
No CSS performance depth issues detected
Network Waterfall
5 requests over 827ms
INFO
0 ms 200 ms 400 ms 600 ms 800 ms FCP 782 ms LCP 782 mshttps://edp.org// https://edp.org/ — 200 — 4.4 KiB — 399 ms — h2https://edp.org/edp.css/edp.css https://edp.org/edp.css — 200 — 397 B — 133 ms — h2https://edp.org/edp.js/edp.js https://edp.org/edp.js — 200 — 3.9 KiB — 133 ms — h2https://edp.org/Image/vim.vialle.love.gif/Image/vim.vialle.love.gif https://edp.org/Image/vim.vialle.love.gif — 200 — 1.4 KiB — 132 ms — h2https://edp.org/favicon.ico/favicon.ico https://edp.org/favicon.ico — 200 — 1.1 KiB — 131 ms — h2
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
49% of JavaScript execution is third-party
First-party Third-party 70ms · 0KB · $1/mo
Unattributable
Other
Optional
Execution 70ms
Transfer 0 KB
Monthly Cost $1/mo

49% 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

How third-party costs are calculated

Real-User Performance (CrUX)
Field metrics from the Chrome User Experience Report
INFO

Chrome User Experience (CrUX)

Real-user metrics from the Chrome UX Report (2026-04-11 — 2026-05-08)

LCP (p75)

1261 ms

91% good

INP (p75)

0 ms

0% good

CLS (p75)

0.000

100% good

FCP (p75)

1264 ms

TTFB (p75)

778 ms

Image Optimization
1 images, 1 KB total, 0 KB wasted
INFO

Image Optimization Audit

Total Images

1

Total Size

1 KB

1 missing dimensions 1 missing lazy loading
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback