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.
Stress test
Fires concurrent requests at /stress at a target rate.
The origin never rate limits that path, so every 429 or 503 you see here came from your
CDN's L7 limiter. Compare the sent count against your origin's access log to confirm the edge shed the load.
Asset gallery
Every asset sits in a different cache tier. Probe one to see the cache headers your CDN
actually returns — the browser cache is bypassed, so you are reading the edge's answer, not a local copy.
Probe the same asset twice to watch Age climb on a cache hit.