How to use
- Pick a target size: S for precision, M as the standard benchmark, L for speed and tracking-style flicks.
- Pick a duration — 30 s is the default benchmark; 60 s shows how your aim holds up as you tire.
- Press Start. A target appears; click it. The next one spawns immediately somewhere else. Misses count against accuracy.
- When the timer ends, read Hits, Accuracy, Avg time to hit and the score. Run it again to compare — same size and time, or it is not a comparison.
- Use your real in-game sensitivity and DPI, in a full-screen browser window, so the movement transfers.
What the trainer measures and how
Every target is drawn on a canvas at a random position, and every click is checked against the target's circle. Four numbers come out of a run:
- Hits — targets you clicked before the time ran out.
- Accuracy — hits divided by all clicks. Clicking the empty canvas is a miss; it costs accuracy but not time.
- Avg time to hit — the mean time from a target appearing to your click on it, timed with
performance.now()from the frame that drew the target. This is the flick metric: it combines reaction, mouse movement and the final correction. - Score — hits weighted by accuracy, so spraying the canvas does not win.
Target size and duration change the numbers a lot, which is why both are chips you set once and keep. Medium targets for 30 seconds is the benchmark setting to compare with friends or with your own past runs.
Flick and tracking — what a browser can and cannot train
Aim has two motor skills. Flicking is one fast movement from where the crosshair is to where the target is, followed by a tiny correction — the CS2 AWP shot, the Valorant Sheriff headshot. Tracking is keeping the crosshair on a target that moves — Apex, Overwatch, spray control. Click-target trainers like this one train the flick and the correction; they do not train tracking, recoil, or anything about game sense.
Honest comparison: dedicated programs such as Aim Lab and KovaaK's render targets in 3D at high frame rates with your exact game sensitivity conversion, offer tracking and switching scenarios, and log progress over months. A browser canvas is 2D, capped by your monitor's refresh rate and the browser's own input path, and knows only one scenario. What it is genuinely good for: a two-minute warm-up before queueing, a quick check whether a new mouse, pad or sensitivity feels better, and a repeatable number to track over time. Treat it as that.
| Setting (M targets, 30 s) | Rough reading |
|---|---|
| Accuracy under 70% | Over-flicking: you pass the target and correct back. Lower sensitivity a notch or slow down the first movement. |
| Accuracy 85%+, slow time-to-hit | Careful but slow. Practise committing to the flick; speed comes before polish. |
| Time-to-hit 400–600 ms | Typical for a warmed-up player on medium targets; sub-400 ms with 90%+ accuracy is a strong run. |
| Numbers swing wildly between runs | Normal for the first two or three runs of a session — that is what the warm-up is for. |
The bands in the table are our observations from the tool's own settings, not a published benchmark; there is no standard dataset for browser aim trainers.
A 10-minute warm-up routine
- Minutes 0–2: large targets, 60 s, then 30 s. Big, easy flicks to wake up the arm. Aim for 95%+ accuracy, ignore speed.
- Minutes 2–5: medium targets, 30 s × 3. The benchmark setting. First run is your cold number; by the third you should be near your usual score.
- Minutes 5–7: small targets, 30 s × 2. Precision. Slow the final correction down; a miss on a small target is almost always over-flick.
- Minutes 7–9: reaction test, two sets of five. Different skill, same warm-up effect.
- Minute 9–10: medium, 30 s, one last run. Note the score. If it is well below yesterday's, it is a sleep or setup problem, not an aim problem.
Keep the same DPI and sensitivity you use in the game; if you play several games, use the eDPI or cm/360 you play most, and convert with the sensitivity converter on this site.
Setup that makes the numbers meaningful
- Full-screen the browser (F11) so the canvas is large and the cursor cannot leave it mid-flick.
- Turn off mouse acceleration in the OS ("Enhance pointer precision" on Windows) — with it on, the same hand movement lands in different places at different speeds.
- 1000 Hz polling and a clean sensor; check both with the polling-rate and mouse tests here.
- High-refresh monitor helps but does not change the comparison between your own runs as long as you don't switch screens.
- Same settings every time. Size, duration, DPI, window size. Change one thing at a time when you experiment.
What makes our aim trainer different
- Time-to-hit measured from the frame that drew the target, with
performance.now(), not from a timer that may fire a frame late. - Accuracy that counts empty-canvas clicks, so the score rewards precision, not spraying.
- Three sizes × three durations on one page, results and a text share, no account.
- No ads on or beside the canvas, nothing spawns or shifts while you play; works with touch too.
- Everything in the browser, loads in a second — fast enough to use before every queue.
Privacy: the run is drawn and scored by the script on this page. No clicks, scores or device data are sent to a server; nothing persists beyond the current tab.
FAQ
Is a browser aim trainer as good as Aim Lab or KovaaK's?
No. Those are 3D, high-frame-rate programs with dozens of scenarios, tracking included, and long-term progress tracking. A browser trainer is a 2D click-target scenario — great for a warm-up and a repeatable measurement, not a replacement for a full trainer.
What is a good accuracy?
On medium targets for 30 seconds, 85–90% with a fast time-to-hit is a strong run in our tool; under 70% usually means you are over-flicking. There is no published standard for browser trainers, so compare your own runs.
Should I use my in-game sensitivity?
Yes — same DPI, no OS acceleration, and a full-screen window. Otherwise the movement you practise is not the movement you use in the game.
How long should I warm up?
Five to ten minutes is enough for most players: large targets first, then medium, then small, plus a couple of reaction-test sets. See the routine above.
Why does my score drop on the 60-second run?
Fatigue and attention. A 60-second run is a good check of consistency; your 30-second score is the one to compare day to day.
Does it work on a phone or tablet?
Yes, with touch. Tapping targets measures a different skill than mouse flicking, so keep phone and desktop scores separate.
