Request waterfall
Fetches every asset tier and API endpoint, then reads the Resource Timing API. Amber = time to first byte, ink = download. A near-zero TTFB after the first run usually means your CDN edge answered.
No measurements yet. Run the waterfall to populate.
Throughput
Random bytes — incompressible on every hop, so the number is honest.
Cache correctness
/api/time is no-store — three hits must return three different request IDs.
/api/config is max-age=30 — a repeat within 30 s means your CDN is caching (that's a pass).
- no-store uniqueness — not run
- cacheable API behaviour — not run
Header inspector
Read what actually arrives at the browser. Look for your CDN's fingerprints:
Age, X-Cache, CF-Cache-Status, Via…
Origin always stamps X-Origin-Server: cdn-testbed.
Origin echo
/api/echo returns what the origin received. Behind a healthy CDN,
client_ip_seen_by_origin should be an edge node, and X-Forwarded-For should carry your real IP.
Mock catalog
/api/products · max-age=120A typical "dynamic" JSON payload rendered client-side — the kind of API response a CDN can safely cache briefly.
Loading catalog…
Asset gallery
three cache tiers
immutable · max-age 1y
immutable · max-age 1y
short · max-age 60s
no-cache · ETag revalidate