How this page was served
Your browser's own timing for this page, then one call to the API, traced from your browser through the Worker to the database.
- Trace ID
not traced yet- traceparent sent
none yet
Page load
Linear scale, measuring…
- DNS lookup…
- TCP connect…
- TLS handshake…
- Request to first byte…
- Download…
This API call
Linear scale, measuring…
- Network to the edge (estimated)…
- Worker in … (fresh isolate: …)…
- D1 query…
- Network back (estimated)…
- Download…
In deployed Workers, timers advance only after I/O, so I/O spans (like the D1 query) are accurate and CPU-only work reads 0 ms.
Your trace is built in memory and sent back to you. I don't store it or your IP address.