VoltReflex: a free reaction time test, and what browser scores really measure

I built VoltReflex, a free visual reaction time test that runs in your browser. The interaction is simple: wait for the screen to turn green, then click or tap. You can choose a session of 5, 10, or 20 rounds, review your best and average times, and share your results.

There is no account to create and no app to download. But a small browser tool like this raises an interesting question: what does the number on the screen actually represent?

The score includes more than your reflexes

A visual reaction test measures the time between a visual cue and an input event. That sounds straightforward, but the path from a browser update to a recorded click includes several steps:

1. The browser schedules and renders the visual change.
2. The display presents that change.
3. You notice the cue and respond.
4. Your mouse, keyboard, or touchscreen delivers the input.
5. The browser processes the event.

Your reaction is part of that chain. Display refresh rate, input hardware, browser workload, and device performance can also influence the result. A browser score should therefore be treated as a practical estimate under your current conditions, rather than a laboratory measurement.

Compare sessions under similar conditions

If you want to compare your own attempts, keeping the setup consistent is useful:

• Use the same device and input method.
• Keep the browser and display settings consistent.
• Avoid switching between a touchscreen and a mouse when comparing scores.
• Take several rounds instead of drawing conclusions from one unusually fast result.
• Pause if you feel tired or find yourself guessing when the cue will appear.

A lower number on a different device does not automatically mean your underlying reaction speed improved. The measurement environment may have changed too.

Why show both best and average times?

The best result tells you about your fastest recorded attempt in a session. The average gives a broader picture of the rounds you completed. They answer different questions, so VoltReflex shows both.

For example, one very quick attempt alongside several slower ones can produce a strong best time without a similarly strong average. Looking at both makes the session easier to interpret than looking at a single headline number.

The 5-, 10-, and 20-round options let you choose between a short check and a longer session. They are not a medical assessment or a way to diagnose a condition.

A small tool with room for feedback

VoltReflex works on desktop and mobile, and the shareable result makes it easy to compare attempts with friends. My aim is to keep the test easy to understand: wait, react, review, and try again if you want to.

You can try the online reaction time test on VoltReflex.

I would appreciate feedback from other developers, especially on mobile usability and how clearly the results explain device-related limitations. If you were presenting browser timing results to users, what context would you include alongside the score?

Disclosure: I am the creator of VoltReflex. This post was drafted with AI assistance and describes the tool's current user-facing features; it is not a technical audit of its timing implementation.