Aim Trainer

This test times a full point-and-click cycle. A target appears, you move your cursor to it, and you click. The moment you click, the next target pops up somewhere else. The score is the average time per target across the run, reported in milliseconds.

That number is not the same as your raw reaction time. Raw reaction time captures only how long your brain takes to notice a stimulus and fire a single response. The aim trainer adds a second, larger cost: the motor movement needed to drag your hand and cursor across the screen and land on the target. Because of that movement component, aim scores are almost always slower than simple reaction scores.

• Detection — spotting the new target.
• Planning — deciding where and how far to move.
• Execution — the physical travel and the corrective micro-adjustments near the target.

The behavior of this test is described well by Fitts’ Law, a model published by Paul Fitts in 1954. Fitts found that the time to move to a target depends on two things: how far away the target is, and how big it is. Small, distant targets take longer; large, close targets are quick.

The relationship is roughly logarithmic. Doubling the distance does not double the time, and a target that is twice as wide is easier to hit than the raw distance would suggest. This is why interface designers use Fitts’ Law to size buttons and place menus. In the aim trainer, the same law governs your average: a run full of tiny targets scattered to the corners will always be slower than a run of large targets near the center.

Fitts’ Law also explains the corrective phase you feel near the end of each move. You launch a fast ballistic motion toward the target, then slow down and make small adjustments to land inside it. Those adjustments cost time and grow as the target shrinks.

Scores vary a lot with hardware and input device, so treat these as rough guides rather than fixed cutoffs.

• Around 600–700 ms per target — casual, often on a trackpad or an unfamiliar setup.
• Around 450–550 ms — comfortable mouse users who play games occasionally.
• Around 350–450 ms — practiced players with a tuned mouse and sensitivity.
• Under 350 ms — well above average, common among dedicated FPS players who train aim regularly.

The test is popular with first-person-shooter players precisely because it isolates the same skill their games reward: getting a crosshair onto a small target quickly and clicking. A single fast run does not prove much; the average over many targets is the honest signal.

Aim is trainable, but gains are gradual and specific to your setup. There is no shortcut that beats deliberate, repeated practice.

• Fix your mouse sensitivity and keep it consistent. Constantly changing DPI resets your muscle memory.
• Use a mouse, not a trackpad, if you want your best number. Trackpads add travel cost and reduce precision.
• Reduce input latency. A wired mouse, a high-refresh monitor, and a game-mode display setting all shave real milliseconds.
• Warm up. Your first ten targets are usually your slowest. A short warm-up run stabilizes the average.
• Aim with your whole arm for large moves and your wrist for fine adjustments. Mixing both smooths the corrective phase.

Be realistic about the ceiling. Human motor speed is bounded, and past a point you are training precision rather than raw speed.

A few habits inflate or deflate your result in ways that have nothing to do with your true aim.

• Panic-clicking before the cursor arrives registers a miss or a slow correction and drags the average up.
• High display or input lag deflates your score without any change in skill; a laggy laptop can add 50 ms or more per target.
• Guessing target positions works until it does not, and a single wild miss can cost more than several good hits saved.
• Comparing across devices. A phone touchscreen, a trackpad, and a gaming mouse produce very different numbers. Compare yourself to your own past runs on the same setup.