How the lab works

Browser → Edge Delivery → Origin

The lab provides controls and short-lived download tickets. The configured delivery hostname serves fixed assets from the origin. Direct origin mode is available before an edge network is connected.

Download benchmark

Choose a fixed asset. Download tickets are valid for a short period and authorize only a predefined test asset. Your browser fetches the full response, counts decoded response bytes and verifies SHA-256. Average Mbps equals received bytes × 8 divided by elapsed seconds and 1,000,000. Timing ends when the body is received, before hashing.

Browser Timing uses Resource Timing where available. Transfer byte counts may include headers; cached or restricted timings may be zero. A three-test sequence is explicitly started by you and stops on error.

Upload benchmark

Your browser generates a 1, 5 or 8 MiB payload in memory. The server streams it through a byte counter and SHA-256 hash. No persistent uploads are created. Browser duration includes the response round trip; server duration measures body processing.

Signed URLs & service limits

A short-lived download ticket authorizes only the selected predefined test asset. If a ticket expires, start a new test to request another one.

Requests are protected by per-client rate limits and concurrency limits. Excessive or automated requests may return HTTP 429 Too Many Requests.

Limits may change over time to protect service availability.

Browser-local history

The latest 20 results stay in localStorage. Clear history removes them. The lab does not send this history to the server. No scheduled measurements or background benchmark requests run.