CognitiveDrill

Reaction Time Test for Gamers

Targets appear anywhere. The clock stops when you hit one, not when you see it.

Settings

Changing one restarts the attempt, and scores set under different settings are not comparable.

Quick start

  1. 1Click Start, then leave the cursor where it is. Do not park it in the middle.
  2. 2Wait. A target appears somewhere random after a short delay.
  3. 3Move to it and click it. The clock runs the whole time your hand travels.
  4. 4A miss does not stop the clock. On Hard the target also expires.
  5. 5After ten targets you get your middle flick time and your miss count.

Hit the target the moment it appears

10 targets, appearing anywhere after 0.8 to 2.5 seconds. Leave the cursor where it lands: recentring between targets flatters the score.

How you compare

Median flick time (ms). Lower is faster. Reference distribution, not CognitiveDrill data.

Median flick time (ms)Reference

The median for this test is 540 ms. Take a run and your score appears on the bar.

Reference distribution, not CognitiveDrill data. It is shaped to match published results for this task and is replaced by our own norms once a cohort reaches n = 1,000. Shape based on: Fitts PM; Elliott D, Helsen WF, Chua R.

Try next

About this test

Why a standard reaction test undersells what gamers do

A normal reaction test puts the target right under your cursor. You never move the mouse, so no movement is in your score.

Games do not work like that. The target appears somewhere you are not pointing, and the clock keeps running while your hand travels.

This test keeps the travel in. So your score here cannot be compared with the simple reaction time test, and it is not meant to be. Subtract one from the other and you get your movement time. That is the part your sensitivity, mouse pad and grip actually change.

Distance and target size do most of the work

The further a target is and the smaller it is, the longer you take to hit it. Paul Fitts put numbers on that in 1954, and seventy years of trying has not broken the rule. It holds on mice, trackpads and touchscreens alike.

One detail is worth knowing. Distance and size do not punish you evenly. Doubling the distance costs less time than halving the target does.

In practice, a small target costs you real milliseconds, and a target at the edge of the canvas costs more than one near the middle. That is why the size setting exists, and why your score only compares against runs at the same size. It is also why grinding tiny targets is a worse use of your time than practising the distance you actually miss at.

What this cannot tell you about your rank

Your browser learns where the mouse is on a schedule set by your operating system and your screen refresh rate. Your mouse's own polling rate barely gets a look in. On a 60 Hz screen a 1000 Hz mouse will not beat a 125 Hz mouse by anything measurable here. In a game running at 240 frames per second you would feel the difference.

This test also ignores tracking, switching between targets, recoil control, crosshair placement and reading the game. Those explain far more of who wins than raw flick speed does.

Treat the number as one honest lap time on one narrow skill. If you want pure aiming with no waiting, the aim trainer drops the delay and times thirty targets back to back.

Getting a fair run

Use the sensitivity you actually play at. Do not lower it to farm a better score. Low sensitivity costs you travel time and high sensitivity costs you accuracy. The setting that gives your best median here is usually close to the one you should be playing on.

Do not move the cursor back to the middle between targets. The delay is random so that pre-aiming does not pay. Recentring turns the test into a fixed-distance drill that flatters you.

For where these numbers sit across the population, see average reaction time by age. Remember its curve comes from tests with no movement in them. What counts as a good reaction time explains why your equipment shifts these figures more than your talent does.

Questions

Why is my score here worse than on a plain reaction time test?

Because this one includes moving the mouse to the target. Expect roughly 200 to 300 ms more than a test where you click in place. That gap is your movement time.

What is a good flick time?

Around 540 ms sits in the middle of the reference distribution at medium target size. Under 450 ms is quick. Compare only against runs at the same target size.

Does a faster mouse help my score?

Barely, in a browser. Your screen and your operating system set how often the browser learns where the mouse is. Hardware that matters in a 240 fps game is mostly invisible here.

Do misses count against me?

The clock keeps running when you miss, so a missed shot costs you time on that target. We also report misses on their own, because a fast median with four misses is not a good run.

Will practising this make me better at aiming in games?

It will make you better at this. Whether it carries over depends on sensitivity, field of view and mechanics a browser cannot copy. Treat any carry-over as unproven.

Sources

  • Fitts PM (1954). The information capacity of the human motor system in controlling the amplitude of movement. Journal of Experimental Psychology, 47(6), 381-391. Link
  • Elliott D, Helsen WF, Chua R (2001). A century later: Woodworth's (1899) two-component model of goal-directed aiming. Psychological Bulletin, 127(3), 342-357. Link
  • Woods DL, Wyma JM, Yund EW, Herron TJ, Reed B (2015). Factors influencing the latency of simple reaction time. Frontiers in Human Neuroscience, 9:131. Link