• Blog
UPGUIDESee plans
Reflexes5 attemptsFree · in your browser

Reaction time test

Measure in milliseconds how long you take from the signal to the click.

Ready

ms

Also try

How the test works

Measures how long you take, in milliseconds, between seeing a signal on screen and clicking. It is the classic reflex test — with one important difference: the number you see is not just your reflex. It includes the delay of your monitor, your mouse and your system, and part of that can be reduced.

How the test works

  • After the first click, the area turns red for a random time between 1.5 and 4.5 seconds.
  • The interval is random on purpose. With a fixed delay you would learn the rhythm and click before seeing the signal — the result would look great and be fake.
  • When the area turns yellow, the timer starts. It stops the instant you click.
  • A click before the signal is detected and discarded, with a warning. It does not count toward the average.
  • The page keeps your best time, average and number of attempts only in the tab’s memory. Nothing is saved and everything is gone when you close the page.

How to read the result

  • The average adult scores around 200 to 250 milliseconds on a visual click test.
  • Between 150 and 200 ms is fast, a common range for people who play FPS games regularly.
  • Consistently below 150 ms is very fast. A single result at that level is usually anticipation, not reaction.
  • Above 300 ms can be fatigue, distraction or hardware delay — worth repeating when rested before concluding anything.
  • A single attempt means nothing. Natural variation between clicks is large, which is why the average of five or more is what matters.

Where this test stops

  • The number is not pure reflex. It adds the time for the screen to show the frame, the time for the mouse to report the click and the time for the browser to process it — that can be 20 to 60 milliseconds of hardware alone.
  • A 60 Hz monitor adds more delay than a 144 Hz one, simply because it draws fewer frames per second.
  • The browser is not the most precise environment for measuring. A test done inside a game, with the system tuned, gives a better result than the same finger here.
  • Fatigue, caffeine, time of day and focus change the result more than any setting does.
  • Do not compare your number with someone else’s on different hardware. It only makes sense to compare you against yourself, on the same machine.

Common problems

My result is much worse than I expected.

Before blaming your reflexes, check the hardware: a monitor at 60 Hz when it could be at 144, a mouse at 125 Hz polling rate, or heavy processes running in the background. Each of those adds milliseconds to the number you just saw.

I keep getting "too early".

You are clicking on anticipation, at the expected rhythm, instead of reacting to the signal. Wait until you see the color change. The interval is random precisely to prevent this.

Can I train and improve?

A little, and quickly at first — but the gains plateau soon. The part of the result that comes from hardware is far easier to reduce than the biological part.

My reaction time is good but I lose gunfights.

Reacting to a click is different from reacting inside a game, where reading the situation, positioning and input lag come into play. If your reflex here is good but in-game it does not seem so, it is worth measuring your system’s input lag instead of training more reflex.

What next?

Did the test find something odd?

Part of the number you saw is your PC, not you. A monitor at a low refresh rate, a mouse at a low polling rate, acceleration turned on and DPC latency add milliseconds before the click becomes an action — and that is system tuning, not training.