What this test measures
Point at a thing, click it, repeat. That is the whole task, and it sounds trivial until you watch your own numbers. The aim trainer shows you thirty circular targets, one at a time, each appearing at a random spot inside the panel. You click each one as fast as you can, and the moment you hit it, the next appears. Your score is the average time per target in milliseconds. A click that lands inside the panel but off the target is counted as a miss, and the page reports your accuracy percentage alongside your time.
Two separate abilities are being combined here. The first is visual search: your eyes have to find the new target, which appears somewhere you cannot predict. The second is motor execution: your hand has to translate what your eyes found into a fast cursor movement that ends inside a 48-pixel circle. Our reaction time test isolates a simpler kind of speed, because there you respond to a single stimulus with a single press and no aiming at all. This test is about pointing, which is a different skill with different bottlenecks.
It also forces a trade-off. Move faster and you miss more; slow down for accuracy and your average climbs. Psychologists call this the speed-accuracy trade-off, and it is the reason the page shows both numbers. A quick average with mediocre accuracy and a slower average with perfect accuracy describe two different strategies, not necessarily two different levels of skill.
Why there is no percentile here
This site follows one rule about percentiles: they appear only when a published research norm exists for the task. For simple reaction time, decades of laboratory data exist, so your score can be placed against real measurements. For a browser aim trainer with 48-pixel targets, thirty trials, and random placement inside a panel, no published normative distribution exists. Nobody has measured a representative population on this exact task and printed the results, so this page shows your score and your personal best, and nothing else.
Inventing a distribution would be easy. Plenty of sites display a smooth curve and tell you that you beat some precise-sounding share of players. Those curves come from self-selected visitors, or from nowhere at all, and their meaning shifts entirely depending on whether the sample is mostly competitive shooter players or mostly people on laptop trackpads. We would rather show you nothing than show you a number we cannot defend.
What the page does track is the comparison that actually holds up: you against yourself. Your personal best and your history come from the same hands, the same mouse, the same screen, and the same panel. When your average drops after a week of practice, the improvement is real. When a stranger posts a faster score, you learn nothing, because you do not know what hardware they were holding.
Fitts's law: why target size and distance decide your time
In 1954, psychologist Paul Fitts had people tap back and forth between metal plates with a stylus while he varied the width of the plates and the distance between them. He found a strikingly regular pattern: movement time grows as the distance to a target grows, and shrinks as the target gets wider. The relationship is logarithmic, which means doubling the distance does not double your time; it adds a roughly constant amount. The original paper is Fitts, P. M. (1954), "The information capacity of the human motor system in controlling the amplitude of movement," Journal of Experimental Psychology, 47(6), 381–391, and it remains one of the most replicated findings in experimental psychology.
The intuition behind it: a pointing movement is not one smooth motion. You make a fast, coarse movement toward the target, then small corrective adjustments at the end. A distant target lengthens the first phase. A small target demands more of the second, because the tolerance for error at the endpoint is tighter. Far and small together is the worst case.
In this trainer, target width is fixed at 48 pixels, so the width term in Fitts's equation never changes. Distance does. Each circle appears at a random position, so the gap between your cursor and the next target varies from a short hop to a full diagonal across the panel. That is why some runs feel fast and others feel slow even when your form is identical: part of your average is the luck of where the circles landed. Averaging over thirty targets matters for exactly this reason, since the random distances even out across a full run.
Mouse settings that change your score
Your score depends on your hardware and settings to a degree that surprises most people, so before you compare a result to anything, know what is under your hand.
DPI and sensitivity. DPI is how many counts your mouse sends per inch of physical movement; sensitivity is how far the system moves the cursor per count. Together they decide how much hand motion a long traverse costs you. Set them too high and the cursor flies past a 48-pixel circle, forcing extra corrections. Set them too low and the long movements eat your time. There is no single correct value, but there is a value your motor system has learned, and changing it throws away some of that learning.
Mouse acceleration. With acceleration on (Windows calls it "Enhance pointer precision"), the cursor travels farther when you move the mouse quickly. The mapping from hand to cursor stops being consistent, so the same physical flick lands in a different place depending on its speed. Fast pointing relies on your brain predicting where a movement will end, and acceleration makes that prediction harder.
Polling rate and refresh rate. A mouse that reports its position infrequently, or a monitor that redraws slowly, adds a small delay between your movement and what you see. These delays are small, but this test is scored in milliseconds.
Trackpad, mouse, or touchscreen. A trackpad gives you friction, a small surface, and a click that takes real force. A touchscreen removes the cursor entirely; you point with your finger, which is a different motor task. Comparing a trackpad score to a mouse score, or either one to a phone score, is not meaningful. Treat scores from different devices as different tests that happen to share a page.
How to actually get faster
Pick a sensitivity and leave it alone. Every change forces your motor system to relearn the mapping between hand and cursor, and that learned mapping is most of what this test measures. Consistency beats endless tweaking.
Use your arm for the big movement and your wrist and fingers for the final correction. Wrist-only aiming works on short hops but runs out of range on long diagonals, and dragging a planted wrist across the desk to reach a far target is slower than a loose movement from the elbow.
Keep your eyes on the target, not the cursor. Your visual system is built to guide a hand toward the point you are fixating; chasing your own cursor with your gaze adds a tracking job you do not need. Snap your eyes to the new circle the instant it appears and let peripheral vision handle the rest.
Warm up before you judge yourself. The first run of a session is usually the slowest, and scores tend to improve over the next few as your movements calibrate. If you want a fair read on your ability, ignore the opening run.
Expect a plateau, because everyone hits one. Early gains come quickly, mostly from fixing strategy: gaze habits, grip, an unsuitable sensitivity. Once those are settled, you are chipping away at small margins of raw motor speed, and progress slows to a crawl. A flat average after weeks of practice is the normal endpoint, not a sign you are doing something wrong.
Frequently asked questions
Is a trackpad slower than a mouse?
For almost everyone, yes. A trackpad offers a few square inches of surface, so long cursor movements need either several strokes or a sensitivity so high that the final correction becomes shaky. The physical click also takes more force than a mouse button and can shift your fingertip as it registers. A practiced trackpad user can post a respectable score, but the same person with a mouse would almost certainly beat it. This is one of the main reasons the page does not rank you against other people: the input device matters too much.
What is a good average time?
We are not going to hand you a number, because any number we gave would be invented. No published norms exist for this task, and results vary widely with device, screen size, and settings. The useful benchmark is your own history. Run the test several times to establish a baseline, then watch whether your average falls while your accuracy holds. Beating your personal best on the same device with the same settings is the one comparison that means something.
Should I click as fast as possible even if I miss?
Misses carry no time penalty; they only lower your accuracy percentage. But every miss means an extra click before the target dies, and those extra movements cost real time inside your average. A sensible approach is to aim slightly faster than feels comfortable and accept a little imperfection. If your accuracy sits at 100 percent, you can probably afford more speed. If it is collapsing, your movements are out of control and the misses are the evidence.
What happens if I pause in the middle of a run?
Nothing stops you, since there is no time limit. But the clock behind the score keeps counting until each target is clicked, so a pause flows straight into your average. If you get interrupted mid-run, the honest move is to finish, ignore that score, and run it again.
Why does the same setup give different scores on different days?
Fatigue, caffeine, time of day, and plain randomness all move the number. Target placement is random too, so one run may contain more long diagonals than another, and Fitts's law says those cost you time through no fault of your own. Single runs are noisy. Trends across many runs are what tell you whether you are actually improving.