How Accurate Are Browser Reaction Time Tests?
The timer measures a browser event. Your screen and input device are part of the result.
What happens between green and your tap?
A browser schedules a visual update, the screen displays it, you see the cue, and your input reaches the browser. The reported interval includes parts of that display and input path. It is not a direct reading of nerve conduction or an isolated measure of your brain.
In React, the game starts its high-resolution clock when the green state is committed, before the browser paints it. The interval ends when the input handler runs. Input is taken on press-down rather than waiting for you to release. That avoids deliberately including the length of your button press, but cannot remove hardware delay.
MDN documents performance.now() as a monotonic clock: it does not jump when the system wall clock changes. Browsers may reduce its precision for security. A precise software clock still cannot determine exactly when a pixel became visible to your eyes.
Does monitor refresh rate affect reaction time?
Refresh rate describes how frequently a display can update. Dividing 1,000 milliseconds by the refresh rate gives the interval between refreshes. These intervals are calculations, not measured input lag or an amount you should subtract from your score.
| Refresh rate | Interval |
|---|---|
| 60 Hz | 16.67 ms |
| 120 Hz | 8.33 ms |
| 144 Hz | 6.94 ms |
| 240 Hz | 4.17 ms |
The cue can arrive at different points within that cycle. Display processing, pixel response, the operating system, and the browser add further complications. Switching from 60 Hz to 144 Hz does not guarantee that your recorded reaction time improves by the difference between those intervals.
Mouse, keyboard, or touchscreen?
Use the input you intend to track over time. React accepts a click, tap, or Space. Changing between them also changes the movement you make, where your hand rests, and the hardware that delivers the input. A phone result and a desktop result can both be valid game attempts without being identical testing conditions.
Reflexable deliberately pools input devices in its public charts. We do not apply a guessed “mobile correction.” If you change setup, treat the next session as a new personal baseline instead of assuming the whole difference reflects a change in your skill.
Can browser tests be useful despite these limits?
Yes: a clearly defined, repeatable game can help you compare your performance on that task. Controlled timing research also shows why software and hardware configuration matter. Bridges and colleagues’ 2020 timing study tested experiment platforms across lab and online environments. It is evidence about those tested setups, not a validation study of Reflexable.
Keep the test in the foreground. Close distracting activity, avoid changing devices mid-session, and compare several completed runs. Internet round-trip time is not added to React’s stopwatch: timing happens locally; sending the completed score to the server is a separate step. A busy browser can still delay rendering or handling input.
Visual reaction, auditory reaction, and reflexes
React asks you to respond intentionally to a visual change. It is often called a reflex test in everyday language, but it does not measure an involuntary reflex such as a knee jerk. An auditory test would present a sound and bring a different audio-output path into the measurement. Reflexable does not currently offer an auditory reaction test.
Do not combine values from different cue types into one average. For interpreting your visual result, see what a good reaction time means. For practicing a particular game, see our consistent-testing routine.