Static probe

CDN / WAF vs direct Vercel

Deploy with vercel, hit this URL through your edge stack and again on the raw *.vercel.app host. Compare numbers below.

Navigation timing (this document)

Values come from the browser’s Performance API; differences mostly reflect network + first byte latency (TLS, routing, WAF, cache).

TTFB (response start − fetch start)
—
DNS + connect + TLS (approx.)
—
DOM content loaded
—
Load complete
—

Subresource check

A second request for CSS exercises connection reuse (or a second edge handshake if HTTP/2 coalescing differs).

Measuring…

Repeated fetch samples

Runs sequential GETs to this path with cache busting (no browser cache). Each bar is TTFB from Resource Timing (responseStart − fetchStart). The dashed line is the average TTFB across successful runs. Short gray bars are failed or untimed requests.