STATISTIK PENGUNJUNG
The HUD numbers, with the ruler beside them
This page reads the same instrument the portfolio HUD paints on its WebGL panel: the telemetry endpoint of the process that is serving you right now. Nothing here is stored, averaged overnight, or rounded into a nicer shape.
NO READING — GET /api/telemetry did not answer this cycle
SERVER ROUND TRIP
ARCHITECTURE TRACE
node = handler duration minus the backend fetch measured inside it; backend = fetch to /api/health; postgres = never measured, the health endpoint answers ok or error without a millisecond figure.
BROWSER FRAME RHYTHM
PROVENANCE
The latency window and the frame window live inside a single Node process, so a second instance keeps its own numbers. Machine identity — build commit, runtimes, heap, the postgres ping — is only sent to a request carrying a valid admin session, so here it is em-dash by design; an empty field is not an old hash or a missing stamp.
HOW EACH FIGURE IS MEASURED
WHAT IS NOT KEPT
The frame window holds numbers only: fps, median, p95, slow-frame count, frames counted and the viewport size they were measured on. No name, no session, no page history and no identity field is accepted — a body carrying anything outside that list is rejected with 400. The IP address is read only as a rate-limit bucket key and is never part of the reported data. Everything above dies with the process.