How the test works
Choose 10, 20 or 30 targets and press Start. A round target appears in the middle of the screen; hitting it starts the run and is not timed, so your hand starts on the target instead of on the Start button. From then on each target appears at a random place, usually at least two target widths away from the last one (on a small screen held sideways it can land closer), and its clock starts with the frame that draws it on the screen. It stops the moment your finger lands or your mouse button goes down on the target.
A press anywhere else on the screen is a miss. The target does not move and its clock keeps running, so a miss costs you the time to correct it, and it is counted in your accuracy. After the last target the screen shows your average and a See result button, and the result card lists the average time per target, the fastest and slowest target, your accuracy and your record for that number of targets on this device.
The targets are always 64 pixels wide, on a phone and on a 27-inch monitor alike, so that the task does not change with the screen. If you switch tabs or the phone locks, the run pauses and the target on screen does not count; tap anywhere for a new one. Esc or the × button leaves without a result.
What the result means
The time per target has two parts: reacting to a target that just appeared, which takes most people 200 to 300 ms, and moving onto it. The movement part grows with the distance and shrinks with the size of the target, a relationship known in ergonomics as Fitts's law. That is why a large monitor with a slow mouse setting gives longer times than a small screen with the same mouse, and why the result is marked approximate. The display, the mouse or touchscreen and the browser add a few to a few dozen milliseconds on top, as in the reaction time test.
- Under 400 ms with a mouse. Fast and precise. Typical of people who play shooters regularly.
- 400 to 650 ms. The usual range for first runs with a mouse.
- Accuracy under 90 %. You are trading precision for speed. Slow down a little; the average usually gets better, not worse.
- A big gap between fastest and slowest. A few targets far in the corners are normal. Many slow ones mean the cursor is getting lost or the mouse is skipping.
How to get a reliable result
Use the setup you want to measure and keep it the same: the same mouse, the same sensitivity, the same browser window size. Full screen gives the most room and the most honest distances. Sit as you would to play, with your wrist or arm resting, and do one run as a warm-up. Turn off pointer acceleration ("Enhance pointer precision" in Windows) if you want results you can compare with other people. Thirty targets give a steadier average than ten; one unlucky target matters less.
When the device is in the way
If the cursor jumps, stutters or stops for a moment during the test, the problem is probably the mouse, not your hand. The mouse test shows the polling rate and catches double clicks from a worn switch, and the refresh rate test shows whether the browser really draws at the rate your monitor promises. A wireless mouse with a weak battery or a receiver far from it, a dirty sensor or a glossy desk can all make the cursor lag behind the hand. On a phone, a screen protector or a wet finger can make touches land late or in the wrong place; the touch screen test shows whether every part of the screen answers.
Frequently asked questions
What is a good score in the aim test?
With a mouse on a computer, most people average between 450 and 650 ms per target on their first runs, and practised players of shooters get under 400 ms. On a phone the numbers are different, because the finger does not have to drag a cursor across the screen. Accuracy matters as much as speed: 95 % or more means you are aiming, not spraying clicks.
Why is my score so different on the phone and on the computer?
They are two different tasks. A finger lands straight on the target, while a mouse moves a cursor that you have to stop on it, and the distance depends on the size of the monitor and the mouse sensitivity. A phone screen is also smaller, so the targets are closer together. Compare results on the same device and with the same mouse settings.
Does a miss make my time worse?
Not directly. A press beside the target is counted as a miss, the target stays where it is and its clock keeps running, so a miss costs the time it takes to correct. The misses lower your accuracy, which is shown next to the average and in the share text, so clicking wildly does not pay off.
Does mouse sensitivity or DPI change the result?
Yes. A very low sensitivity makes long moves slow and a very high one makes you overshoot and correct. Pointer acceleration in Windows or macOS also changes how far the cursor travels for the same hand movement. Pick the settings you actually play with and keep them the same between runs, otherwise you are measuring the settings, not your aim.
Is my aim score saved?
Only your best average for each number of targets, in your browser's local storage on this device. Nothing is sent anywhere and there is no leaderboard. Clearing site data removes it. A private window cannot see it, and a record set in one is lost when the window closes.