Aim trainer
Pick a mode, a duration and a target size, then click every target that appears as fast and accurately as you can. Hits, misses, accuracy, targets per second and average time-to-hit are all tracked live, and your best hit count is saved per mode and duration.
No score yet for Flick · 30s
Round summary
Flicking vs. tracking, and why this tool focuses on flicking
Mouse aim in most fast-paced games splits into two distinct skills. Flicking is the snap movement from wherever your cursor currently rests to a new target that just appeared — a cold start, no warm-up, judged on how quickly and precisely you land the very first shot. Tracking is the opposite: keeping a cursor glued to a target that is already moving, a continuous correction rather than a single jump.
Flick mode on this page isolates the first skill directly — one target, one flick, repeat. Grid mode is a related but different drill: three static targets are live at once, so beyond the flick itself you're also deciding which target to take first, and your eyes have to re-acquire a new point after every hit instead of following one moving object. Neither mode simulates true tracking, which needs a target that moves continuously rather than one that waits in place — that's a deliberately different tool, out of scope here.
Reading the accuracy-vs-speed trade-off
Two rounds can have the same hit count and tell very different stories. Someone who clicks carefully might land 24 hits out of 26 clicks — 92% accuracy — while someone clicking faster and looser might land 24 hits out of 40 clicks, 60% accuracy, in the same amount of time. Both scored 24 hits, but the first person is more precise and the second is faster at generating attempts. Neither number alone tells the full story; read hits, accuracy and targets-per-second together, not in isolation.
A practical rule of thumb: if accuracy drops sharply when you push for a higher hit count, you're past the point where more speed is helping — dial the target size up a step or slow down slightly until accuracy recovers, then push speed again from there.
The honest caveat: your numbers are device-dependent
This tool measures what actually happens between your input device and this browser tab, and that path is not the same on every setup. Two things matter most:
- Display refresh rate. A target can't be clicked before it's visible, and it isn't visible until a frame paints it. On a 60Hz display that can hold a freshly spawned target invisible for up to roughly 16.7ms longer than on a 144Hz or 240Hz display — time that shows up in your average time-to-hit even though nothing about your reaction changed.
- Input latency. Mouse polling rate, wireless versus wired connections, OS-level pointer acceleration or smoothing, and general system load under a busy browser tab all add small, variable delays before a click reaches this page's event handlers.
None of this is specific to this tool — every browser-based reaction or accuracy test sits downstream of the same chain. It's why the numbers here are most useful for tracking your own progress on your own setup over time, and worth treating with more caution as a direct comparison against someone using different hardware.
Tips for getting more out of a session
- Warm up before you judge a score. The first round after opening the page is rarely your best — your hand hasn't calibrated to this particular target size and arena yet.
- Isolate one variable at a time. If you change target size and duration in the same session, you won't be able to tell which change moved your accuracy. Hold one constant while you vary the other.
- Use 15s rounds to test peak speed, 60s rounds to test consistency. A short round rewards a fast burst; a long round exposes fatigue and drift that a 15-second sprint never reveals.
- Compare targets-per-second and accuracy together, never one alone. A higher hit count with falling accuracy usually means you've overshot your current control — the trade-off section above walks through why.
- Take breaks. Repeated fast clicking is a repetitive motion. If your hand or wrist starts to feel strained, stop — no score here is worth an injury.
Frequently asked questions
What's the difference between Flick and Grid mode?
Flick mode shows exactly one target at a time — hit it and the next one spawns immediately somewhere new, which isolates the single skill of snapping your cursor from a standing start onto a fresh point. Grid mode keeps three targets live on screen at once; hitting any one of them spawns its replacement while the other two stay up, which is closer to clearing several threats in quick succession and rewards target selection as well as raw speed.
How is accuracy calculated?
Accuracy is hits divided by total clicks (hits plus misses), shown as a percentage. A click that lands on a target counts as a hit; a click anywhere else inside the play area while a round is running counts as a miss. Clicks before you start or after the round timer ends aren't counted either way.
What does "targets per second" measure?
It's your hit count divided by the round's fixed duration — not by however many milliseconds a timer happened to measure, so a 30-second round always divides by exactly 30. It's a throughput number: how many targets you cleared per second of the round, independent of how many misses you also made along the way. Pair it with accuracy to see whether you're trading speed for precision or genuinely faster at both.
How is average time-to-hit measured?
For each target, the clock starts at the timestamp of the click that caused it to spawn (the previous hit, or the Start button for the very first target) and stops at the timestamp of the click that hits it. Both of those timestamps come from the browser's own event.timeStamp property on the actual pointer events — not from a requestAnimationFrame callback and not from Date.now() — because a frame callback can lag the real input by a frame or more, and this tool wants the moment the input was received, not the moment a frame happened to redraw.
Does my display's refresh rate or input lag affect my score?
Yes, and there's no way around that from inside a web page. A target only becomes visible after a frame paints, so a 60Hz display holds a newly spawned target invisible for up to ~16.7ms longer than a 144Hz or 240Hz display would, and that gap shows up in your average time-to-hit whether or not your reflexes changed at all. Mouse polling rate, OS-level pointer smoothing and general system load add their own small, variable delays on top. Treat scores as meaningful for comparing your own runs on your own setup over time, and be cautious comparing a number here directly against someone on different hardware.
What target size should I practice with?
Small targets push flicking precision the hardest and will usually show the biggest accuracy drop; large targets let you focus purely on speed since landing on them is easier. There's no single correct choice — a common approach is running a few rounds at each size back to back so you can see how your accuracy-versus-speed trade-off actually shifts as the hit-box shrinks, rather than guessing.
Where is my best score saved, and can I lose it?
It's written to your browser's own local storage, one entry per mode-and-duration combination (Flick/15s, Grid/60s, and so on are tracked separately), and read back only by this page in this browser. It never leaves your device and isn't tied to an account, so clearing your browser's site data, using a different browser, or switching to a private/incognito window will all show no saved best.
Does this work on a touchscreen or trackpad?
Taps and trackpad clicks both register as clicks, so the tool runs on either. That said, a touchscreen or a trackpad is a genuinely different input than a mouse — different precision, different latency characteristics — so don't expect the numbers to translate directly between input devices; treat each as its own baseline.
Is this a substitute for aim-training software built into a game?
No. This is a simple, general-purpose flicking and target-acquisition drill that runs in a browser tab — it doesn't replicate a specific game's sensitivity curve, hit registration, weapon spread or field of view, and it never claims to. It's useful as a quick, no-install warm-up or a way to track your own progress over time, not as a stand-in for practicing in the actual game you play.
Use cases & limitations
Where this is useful
- A quick warm-up. A minute or two of Flick mode before a session is a common way to get your hand calibrated before something that actually matters.
- Tracking your own progress. Because best scores are saved per mode and duration, you can watch a specific combination — say Flick at 30s, medium targets — trend over weeks.
- Comparing target sizes on your own setup. Running the same duration at small, medium and large targets shows you where your accuracy actually starts to fall off, rather than guessing.
- A no-install, cross-platform baseline. Nothing to download; it runs the same way in any modern browser.
What this tool can't tell you
- Your true reaction time or hardware ceiling. Display refresh rate and input latency are part of every number this page produces — see the caveat above.
- Real tracking-aim skill. Every target here is stationary once it spawns; nothing here tests following a continuously moving point.
- How you'll perform in a specific game. Sensitivity curves, hit registration and field of view all differ per game and aren't modelled here.
- A verified or competitive score. This is a casual self-measurement tool with no anti-cheat or verification layer of any kind.