How good is your aim?
Hit the targets in 30 seconds. Track your hits, misses and accuracy.
Preparing test…
This is a pointer/touch aiming test. It cannot be performed with a keyboard or screen reader.
Reading your aim: speed and accuracy pull against each other
The test reports two numbers that trade off — how many targets you hit, and what share of your clicks actually landed on one.
What this measures
Over 30 seconds it counts every target you hit and every click that missed. Accuracy is hits divided by all clicks; hits-per-second is hits divided by the full 30-second run. Targets appear at random positions sized to stay fully on screen, so no target is ever placed out of reach.
How to read your result
- High hits-per-second with low accuracy usually means you are clicking ahead of the cursor — slowing slightly often raises both numbers at once.
- Accuracy near 100% with low hits-per-second means you are careful but leaving speed on the table.
- Because target positions are random, one run is a small sample. Compare several before reading a trend.
How your score compares
There is no universal “good” aim score: it depends on your mouse sensitivity, screen size and pointer settings. The only fair comparison is against your own earlier runs on the same setup.
Practical tips
- Lower your mouse sensitivity or DPI a little for fine targeting; very high sensitivity makes small corrections overshoot.
- Move from the elbow for large sweeps and from the wrist for small adjustments.
- Keep a relaxed, consistent grip — tension costs precision.
A trackpad or touchscreen behaves very differently from a mouse, so the score reflects your input device as much as your aim. It is practice feedback, not a competitive ranking. See the full method →
Use a result as a starting point
Aim accuracy is hits divided by all attempts. Hits per second uses the full 30-second run. Compare your own results with the same input type.
Does this measure hardware latency or polling rate?
No. Browser event delivery is affected by scheduling and input processing. These tools do not certify hardware latency, USB polling rate, DPI accuracy or switch lifespan.
Where do my results go?
The last 30 runs stay in this browser’s local storage. Use the history button to copy a readable report, export JSON or remove them. Raw keyboard and pointer event streams are not sent to a server by this app.