A reaction time test measures the exact interval, in milliseconds, between a visual go signal appearing on screen and the moment you press a key, tap, or click in response. Browser-based tests display a single large panel, hold it on a waiting color for a randomized period, then flip it to a bright green "press now" state, and time how long it takes your input to arrive. Tools that record recent attempts, a best score, and a running average give you a usable baseline you can compare across sessions and devices. The Reaction Time Test from Lizely works exactly this way and keeps every measurement local to your browser.
Reaction time matters any time you make a fast choice under a visual cue — driving, gaming, sports, or simply noticing whether your reflexes feel sharper on one device than another. A test gives you a number instead of a feeling, so you can spot real changes (tiredness, a new keyboard, a higher refresh-rate display) instead of guessing. The rest of this guide explains what the test measures, how to run it correctly in three short steps, how to read the recent-best-average readout, and how to compare results honestly.
What the Reaction Time Test Actually Measures
The panel starts in a neutral waiting state. After a short randomized delay it switches to green and shows a clear "PRESS NOW" prompt. The tool records the number of milliseconds between that color change and the moment your press (click, Enter, or Space) reaches the page. That single number is your reaction time for that attempt.
A reaction-time measurement has three parts you should understand before you start clicking:
- Stimulus onset. The exact moment the panel turns green. The browser timestamp on this event is the start of your measurement.
- Response onset. The exact moment the browser receives your keydown or click event. This is the end of your measurement.
- Reaction interval. The difference between those two timestamps, reported in whole milliseconds.
Only the interval between stimulus and response is your score. Network lag, page load, and rendering time are not part of the number — the timer begins when the panel actually changes color, not when the page first loaded. If you want to read more about how browsers expose timing data, the MDN Web Docs site is a reliable starting point.
Run the Reaction Time Test in Three Steps
The test is deliberately simple so the only variable it measures is you. Follow the same routine for every attempt you want to compare later.
- Click Start test and leave the panel visible. Resist the urge to press anything while the panel displays the waiting message. The wait uses a randomized delay so you cannot time the green by counting or rhythm. Cover the panel with your other hand if you find yourself tempted to anticipate.
- Press the panel, Enter, or Space the instant it turns green and shows PRESS NOW. Use whichever input feels most natural — click the panel with the mouse, or rest a finger over Enter or Space and tap down the moment the color flips. The timer records your input as soon as the browser receives the event.
- Repeat under identical conditions. Run at least five attempts in a row, on the same device, browser window size, keyboard, and seating position. After each press the tool shows the latest interval; after several attempts it also reports your best score and your running average. Use Reset all when you want to clear those values and start a clean baseline.
If you want a fair comparison across days, do the same warm-up, the same number of attempts, and the same input method each time. Switching from Space on a laptop keyboard to a click on a trackpad will change your number even if your reflexes are identical.
Reading the Recent, Best, and Average Values
After a few attempts the panel surfaces three numbers. Each one tells you something different and they are not interchangeable.
| Reading | What it shows | When it is most useful |
|---|---|---|
| Latest | The millisecond interval from your most recent attempt only. | Spotting whether a single attempt was unusually fast or unusually slow. |
| Best | The fastest interval recorded in the current session. | Showing your ceiling when you are warmed up and focused. |
| Average | The mean of your last five intervals. | Tracking day-to-day change in your baseline reflex speed. |
One unusually fast or slow attempt should not change your interpretation of the session — the average smooths those out, and the best score exists only to mark your peak. If you want to compare results across browsers, run the same five-attempt set in each one and read the average; a single number per browser is far more honest than a single "best" number that may have been a lucky guess.
How to Compare Results Honestly Across Sessions
The biggest source of false conclusions is comparing measurements made under different conditions. A change of 30 ms between sessions is meaningless if one session was on a 60 Hz laptop screen, the other on a 144 Hz external monitor, and a third on a phone. Lock down as many variables as you can before you draw conclusions.
A practical baseline routine looks like this:
- Same device and input. Use the same physical keyboard or mouse every time, and pick one input method — click, Enter, or Space — and stick with it.
- Same window state. Keep the browser window the same size, in focus, and not behind another tab. Background tabs throttle timers and will add unwanted delay.
- Same warm-up. Take two or three "throwaway" attempts to get over the startle of the first press, then record the next five as your set.
- Same time of day. Reaction time varies with sleep, caffeine, and fatigue, so compare mornings to mornings rather than morning to late night.
If you only need a single sanity check, five attempts is enough to see a stable average. If you are comparing two browsers or two keyboards, run ten attempts per condition and rely on the average rather than any single best score. For more on how click speed varies with input style, see the guide on the CPS Test 1 Second, which uses the same input-timing approach over a one-second window.
What a "Good" Reaction Time Looks Like
Most healthy adults score somewhere between 200 and 300 milliseconds on a clean visual test of this kind. Anything under 250 ms is generally considered quick, anything over 350 ms suggests fatigue, distraction, or a setup issue such as a high-latency input device. These are rough bands, not hard thresholds, and they apply to a single-focus visual test like this one — not to a complex choice task with several stimuli.
If your average is consistently above 400 ms, the most likely culprit is not your reflexes but your setup: a wireless mouse with polling issues, a sticky modifier key, or a browser tab that is not in focus. The Keyboard Tester can confirm whether a key is registering cleanly on the first press, and the guide to testing mouse buttons in your browser walks through checking the mouse side in the same way.
Common Setup Problems That Inflate Your Score
A surprisingly high reading usually traces back to one of a handful of mechanical issues rather than slow reflexes. Check these before assuming your baseline has slipped:
- The tab is not in focus. Background tabs run at throttled frame rates and add tens of milliseconds to any visual cue. Click the panel before you start to make sure the tab is active.
- Your finger is not already on the key. Moving your hand from the desk to the keyboard costs roughly 80–150 ms. Rest a finger on Space or Enter between attempts.
- You are pressing before the green. Anticipating the color flip is the single biggest source of false-high scores. The waiting message is there specifically to break any rhythm you try to lock onto.
- Display refresh rate is low. A 60 Hz monitor updates the panel only every ~16 ms, which is fine, but a dim or motion-blurred screen can make the green harder to spot in time.
Once those are controlled, the test reflects what you actually want to know: how quickly your brain and fingers respond to a single visual cue.
Putting It Together
A clean reaction-time number comes from a clean test. Use the same input, the same browser, the same window state, and a randomized-delay tool like the Reaction Time Test, and trust the average of five attempts over any single score. Run it the same way once a week and you will have a baseline you can actually act on — whether you are chasing better gaming reflexes, checking whether a new keyboard slows you down, or just curious how sharp you feel today.