Measurement

How a number from a browser gets produced, and what it can and cannot tell you. Apparatus effects, timing precision, latency, and why browser scores are not laboratory scores.

A browser reaction test is a timing instrument, and like any instrument it has error bars that are rarely zero. This topic is about where those error bars come from — how long a pixel takes to change, how long a mouse takes to report a press, and what a JavaScript timer can and cannot resolve — and how much of that error you can measure and subtract.

The practical consequence runs through everything else on this site. A browser number is not a laboratory number, the gap between them is large enough to matter, and no amount of careful clicking closes it. What it does support is comparing you against yourself on one setup, which is the comparison every test on this site is built for.

Everything here traces to a specific documented limitation, with the size of the effect stated where it is known, so you can decide which parts of a score to trust.

4 articles

7 min read

How Input Latency Compensation Actually Works

A median of five real clicks, subtracted from every result. What that measures, what it cannot reach, and how to get a clean latency reading on your own setup.

6 min read

Why Anticipation Is the Only Cheat That Matters

A randomised 1–3 second delay is what separates a measurement from a guess. How the too-early detector works, and the corner case a pre-timed press can still get through.

6 min read

What Your Browser Cannot Measure

Six real limitations of browser-based timing, how large each one is, and why that does not undermine the one comparison that matters: you against yourself.