Aim Trainer
Hit 30 targets as they jump around a fixed field and read your median time per target.
A pointing task: press the targets with a mouse, a trackpad or a fingertip. Keyboard presses are not scored, because keyed aiming and pointed aiming are different tasks and would not compare. Begin, stop and test again all work from the keyboard.
This measures how long it usually takes you to spot a new target, move onto it and hit it. 30 targets, less time is better.
- Press the target in the middle of the field to begin
- Hit the target wherever it jumps to; a press that misses leaves it where it is
- Finish all 30 and your time per target appears
How to read your score
| Score | What it means |
|---|---|
| Under 420 ms per target | Under 420 milliseconds per target is the fastest of the five bands this aim trainer uses, and 30 targets at that pace take under 13 seconds in total. It means a target roughly 150 pixels away was spotted, travelled to and hit in under half a second, thirty times over. The band describes your own median time, not a ranking against other players. |
| 420 to 520 ms per target | 420 to 520 milliseconds per target is the second of the five bands this aim trainer uses; 30 targets at that pace take roughly 13 to 16 seconds in total. Read it together with the hit rate beside it, and compare it with your own recent runs on the same pointing device rather than with a figure quoted on another site. |
| 520 to 640 ms per target | 520 to 640 milliseconds per target is the middle of the five bands this aim trainer uses, and 30 targets at that pace take roughly 16 to 19 seconds. A mouse time and a touchscreen time are two separate readings rather than one that got worse: steering a cursor onto a target and landing a fingertip on one are different motor tasks. |
| 640 to 800 ms per target | 640 to 800 milliseconds per target is the fourth of the five bands this aim trainer uses; 30 targets at that pace take roughly 19 to 24 seconds. Check the hit rate next to the score before reading anything into it, because time spent on presses that missed is inside the number: a miss leaves the target where it is and the clock keeps running. |
| 800 ms per target and over | 800 milliseconds per target or more is the slowest of the five bands this aim trainer uses, and 30 targets at that pace take 24 seconds or more. Anything that makes the pointer harder to place is inside that number - an unfamiliar trackpad or stylus, a device you picked up today, a screen held at arm's length. Run it again on the same setup before treating one run as a reading. |
These five bands are time ranges for this site's own version of the task: a 320 pixel field, a 64 pixel target, and 110 to 190 pixels between targets. They are not norms, not pass marks, and they do not say how many people you outpaced - this release has no reference sample, so it shows no percentile rather than inventing one. A single run also swings on its own, so read several of your own runs on the same device and the same pointing device before deciding anything has changed.
How to play
- Press the target in the middle to start: Every run opens with a single target at the exact centre of the field. Press it and the practice targets begin straight away. Starting from the centre also means your pointer begins every run in the same place, so the distance to the first target is the same one everybody else travels.
- Warm up on five practice targets: Five practice targets behave exactly like the scored ones and none of them counts. They cannot be skipped: everybody gets the same warm-up, so nobody's score is quietly helped by having already found their rhythm.
- Hit the 30 scored targets: Each hit makes the next target appear somewhere else on the field, between 110 and 190 pixels away. Press inside the circle to hit it. A press that lands in the field but off the circle is a miss: the target stays exactly where it is and nothing on screen points you towards it, so keep watching the whole field rather than one corner of it.
- Read your time per target: Your headline number is the median of your scored targets in milliseconds - the middle value once every target's time is sorted, so one slip does not drag it around. Next to it you get your hit rate, your fastest single target and how many targets counted towards the score. Lower is faster, and the band table below says what your number works out to.
What this measures
The field is 320 by 320 pixels and every target is 64 pixels across, on a phone and on a desktop alike. Neither scales with your display: a target that shrank on a small phone would be a harder task wearing the same score.
Consecutive targets are always 110 to 190 pixels apart, centre to centre, and every target sits fully inside the field. That range is the whole difficulty setting: there is no easy mode and no hard mode to pick between.
A press inside the circle is a hit and stops that target's clock. The clock started the moment the target was really on your screen, so nothing that happened before it appeared is charged to you. A press inside the field but outside the circle is a miss: it counts against your hit rate, the target does not move, and no hint tells you where to look.
A hit that lands less than 150 milliseconds after the target appeared is treated as a press that was already on its way rather than a reaction to the target. That target is used up, it is not re-run, and it does not count towards your score.
A target nobody hits within 5 seconds times out. It is used up too, and the run moves straight on to the next one.
Presses within 80 milliseconds of a hit, or within 110 milliseconds of the previous press, are ignored: not a hit, not a miss. Machine-gunning the field therefore gains you nothing, and the run keeps count of how many presses it ignored.
A run only gives you a number when at least 27 of the 30 targets produced a usable time, at least half of your hits and misses together were hits, fewer than 15 presses were ignored, and the scored block finished inside 60 seconds. Miss any of those and the screen tells you which one instead of handing you a score.
Stay on this page until the run ends. Switching away, refreshing or stopping ends the run without saving anything, and the timing is not picked up where it left off - nobody was looking at the screen during that gap.
Mouse runs and touchscreen runs are recorded separately, each with its own best. Moving a cursor onto a target and putting a fingertip on one are different motor tasks, not fast and slow versions of the same one.
To compare two of your own runs, keep the device, the pointing device, the screen and the way you hold it the same. Change any of those and you are comparing setups as much as aiming. Your results stay on the device you played on, so a different browser or a cleared history starts you with an empty record.
FAQ
What is an aim trainer test?
An aim trainer test times how long you take to move onto a target and hit it, over and over. This one gives you 30 targets on a fixed field, times each one from the moment it appears to the press that lands on it, and reports the median of those times in milliseconds next to your hit rate. It is the classic pointing task used to study aimed movement, not a mode borrowed from any particular shooter.
What is a good time per target on an aim trainer?
Lower is faster: on this test anything under 420 milliseconds per target falls in the fastest of five bands, and 420 to 520 is the band above it. What the test cannot tell you is where you sit among other people, or what is normal for your device, because it has no reference sample and shows no percentile. Compare several of your own runs on the same device instead of chasing a number quoted elsewhere.
Why are aim trainer times different on every site?
Because the task is not the same size from one site to the next. How long a target takes depends on how far you travel and how big the target is, the relationship Paul Fitts described in 1954, so a wider field or a smaller target stretches every time without your aiming changing at all. This test fixes the field at 320 pixels, the target at 64 pixels and the gap between targets at 110 to 190 pixels on every screen, which is why times measured here only compare with other times measured here.
Do aim trainers improve your aim in games?
This test cannot tell you that, and it does not claim it. It reports how long you took to hit 30 targets on this page today, and says nothing about how you will perform in any game. Claims that browser aim training carries over to game aim circulate widely, but the public support for them is press coverage rather than peer-reviewed evidence, so no such claim is made here. What a run does give you is a repeatable measurement of one narrow skill: putting a pointer on a target that just appeared.
What does an aim trainer measure - reaction time or aiming?
Both, mixed together, and that is what the number means. Each target's time contains spotting it, the movement towards it and the correction at the end, which is why this kind of task is often called a hand-eye coordination test. If you want the spotting part on its own, a simple reaction time test is the task for that; this one is about the movement that follows. Either way the score describes this task on this setup, not your coordination in general.
Can a mouse aim time be compared with a touchscreen one?
No, and this test keeps them apart on purpose, with a separate record for each. Steering a cursor with a mouse and landing a fingertip on glass are different motor problems: the finger also covers the target as it arrives, which changes how the last few millimetres are corrected. A trackpad is a third case again, and it is recorded as a mouse run, so keep the same pointing device across any runs you intend to compare.
How do you practice aim without losing accuracy?
Watch the hit rate next to the score, not the milliseconds alone. A missed press leaves the target in place and the clock running, so spraying the field makes your time worse rather than better, and half your presses missing ends the run with no score at all. A few runs on the same device, with the same grip and the same screen, tell you more about your aim than a long session on whatever hardware is to hand.
Why do some aim trainer runs not get a score?
Four things end a run without a number: fewer than 27 of the 30 targets produced a usable time, fewer than half of your hits and misses together were hits, 15 or more presses arrived too fast to be aimed, or the scored block ran past 60 seconds. Each one closes a way of producing a fast-looking number without doing the task, and the screen tells you which one it was.
Related games
ReactionChoice Reaction Time TestFour shapes, four keys - press the one that matches.PlayAbout 45s
ReactionReaction Time TestWait for green, then press. See how quickly you react.PlayAbout 45s
AttentionSchulte TableTap 1 to 25 in order on a shuffled grid and read your time in seconds.PlayAbout 40s
MemoryDigit Span TestDigits flash one at a time. Type them back in order and see how long a string you can hold.PlayAbout 60sThis test is for self-knowledge and practice only. It is a non-standardised adaptation, not a clinical or intelligence assessment, and the result cannot be exchanged with a clinical scale.
Last updated: 2026-09-21 · Scores stay on this device