Hit thirty targets as quickly as you can. The clock starts on your first hit.
Last updated 3 September 2026
Speed against accuracy
There is a well-documented trade-off between how fast you move a pointer and how reliably you land it, described by Fitts's law: the time to hit a target grows with distance and shrinks with size. That is why this test reports both numbers rather than one. Pushing your average time down is easy if you stop caring where the clicks land, and pushing accuracy up is easy if you move slowly — the useful score is the one where both hold. Targets get slightly smaller as the run goes on, which tightens the trade-off rather than simply making things harder.
What the score is made of
A click-accuracy score combines three separate skills that improve at different rates. Target acquisition is how quickly your eyes find the next target — largely a matter of where you are looking and how wide your attention is spread. Movement is getting the cursor there, which follows Fitts's law: the time required grows with distance and shrinks with target size, in a relationship consistent enough to be a design principle in software interfaces. Correction is the small adjustment at the end, and it is where most wasted time hides.
Overshooting and correcting back costs far more than a slightly slower initial movement that lands accurately. Most people improve fastest by deliberately slowing the final third of each movement rather than by trying to move faster overall.
Setup matters more than most people expect
Mouse sensitivity is the biggest single variable. Very high sensitivity makes long movements fast but small corrections nearly impossible; very low sensitivity makes precision easy but forces large arm movements. Most people who take aim seriously settle far lower than they expect and use the whole forearm rather than the wrist.
Consistency is what actually produces improvement, though. Changing sensitivity frequently resets the muscle memory you are trying to build, so picking one setting and staying with it for weeks beats chasing an optimal number. And treat the score as a comparison against your own past results only — display refresh rate, mouse polling rate and input latency vary enough between setups that cross-machine comparisons mean very little.
Common questions
What is a good average time?
Most people land somewhere between 500 and 800 milliseconds per target on a mouse. Under 400 is quick. Touchscreens are generally slower because the finger has to travel and land rather than the cursor being dragged.
Do misses end the run?
No. They are counted and reported as accuracy, but the run continues. Ending on a miss would push everyone towards slow, careful clicking, which measures patience rather than aim.
Why do the targets get smaller?
To keep the difficulty rising in a way that tests precision rather than just reaction. A smaller target takes longer to hit for the same distance, which is the core of Fitts's law.
Does it work on a phone?
Yes, taps work the same as clicks. Times will be slower than on a mouse, so compare phone runs against phone runs rather than against desktop scores.
What is the fastest way to improve?
Work on the final correction rather than raw speed. Overshooting a target and adjusting back costs more time than a slightly slower movement that lands accurately, so deliberately controlling the last third of each movement usually produces the biggest gain.
What mouse sensitivity should I use?
Lower than most people expect, with movement coming from the forearm rather than the wrist. High sensitivity makes fine correction very difficult. More important than the exact figure is keeping it constant, since changing it resets the muscle memory you are building.
Can I compare my score with someone else's?
Not meaningfully. Display refresh rate, mouse polling rate, input latency and pointer settings all affect the result. The score is useful as a measure of your own progress on one setup rather than as a comparison between people.