Reaction time is the delay between noticing a signal and beginning a physical response. In a simple visual test, the signal is usually a color change and the response is a mouse click or screen tap. The number looks precise, but it combines several different delays. Your attention and nervous system matter, and so do the display, browser, operating system, and input device.
That is why a useful reaction-time result is not a universal label. It is a repeatable measurement taken under known conditions.
A practical way to read the number
For a basic online visual test, many alert adults produce five-round averages somewhere around 200 to 300 milliseconds. Results below that range can occur with practice and responsive hardware. Results above it are not automatically bad: unfamiliar instructions, a touch screen, a slow display, fatigue, distraction, and accessibility needs can all add time.
Treat broad ranges as context rather than a diagnosis:
| Five-round average | Practical interpretation |
|---|---|
| Under 180 ms | Very fast for a browser-based visual test; verify with repeated rounds |
| 180-230 ms | Fast and often associated with focused, practiced attempts |
| 230-300 ms | A common everyday range under ordinary test conditions |
| 300-400 ms | May reflect caution, distraction, touch input, or added device delay |
| Over 400 ms | Repeat after a warm-up and check the testing conditions |
These bands are deliberately approximate. They are not medical reference values, and Mini Test Lab does not use them to assess health or fitness to perform a task.
Why one attempt is not enough
A single trial is strongly affected by anticipation. You may click early because you expect the signal, or hesitate because your attention briefly moves elsewhere. The browser may also present the signal just after a display refresh, adding almost a full frame before you see it.
Use an average of at least five valid trials. Discard early clicks rather than assigning them a reaction time. If one trial is dramatically slower because of a clear interruption, repeat the complete set instead of deleting only the unfavorable number.
Consistency is often more informative than a personal best. Five results clustered between 225 and 240 ms describe performance better than one 170 ms result surrounded by much slower attempts.
Hardware changes the score
A 60Hz display draws a new frame about every 16.67 ms. A 120Hz display does so about every 8.33 ms. Higher refresh rates can reduce the waiting time before a visual change appears, but they do not remove browser, system, input, or human delay.
Input method matters as well. A mouse button may report more quickly and consistently than a touch screen. Wireless power saving, display processing, remote desktops, and heavily loaded systems can add further delay. These differences make cross-device comparisons unreliable unless the purpose is specifically to compare devices.
How to establish your baseline
- Use the same computer, display, browser, and input device.
- Close demanding applications and keep the test tab visible.
- Complete one warm-up set without recording it.
- Run three five-round sets with a short rest between them.
- Record the median of the three averages.
The median is the middle result after sorting the three averages. It limits the effect of one unusually good or bad set.
When to retest
Retest when you change a display mode, mouse, browser, or system setting. Retesting can also show how sleep, fatigue, and distraction affect consistency, but do not use an informal web test for safety-critical decisions.
If you are investigating a large difference between two devices, start with the monitor refresh-rate test and then read how device latency affects reaction time. The goal is not to chase the smallest possible number. It is to understand which part of the testing system changed.