Flick arena
Sixteen alternating targets
Click to start. Flick to each target as it alternates left and right.
Complete 16 flicks for a sensitivity verdict.
Mouse Flick Test
This mouse flick test tracks your cursor path to each target. Click to start. Targets appear alternately left and right at random distances, so the arena knows whether you flew past the target or stopped short before correcting.
Flick analysis
- Overshoots
- 0
- Undershoots
- 0
- Hits
- 0
- Avg horizontal error
- --
- Progress
- 0 / 16
Get a useful flick reading
1. Flick, do not track
Move to the target in one motion and click. Slow dragging defeats the purpose.
2. Keep the same grip
Changing from wrist to arm aiming mid-test confuses the result.
3. Read the verdict
Mostly overshoot means lower sensitivity. Mostly undershoot means raise it slightly.
How overshoot is measured
Path tracking
The furthest point your cursor reached beyond the target is recorded, even if you corrected back.
Both directions
Targets alternate so left-hand and right-hand flicks are both tested.
Random distance
Prevents you from learning a fixed motion.
Direct sensitivity advice
The verdict tells you which way to move your setting.
Flick terms
- Flick
- A single fast movement to a target with no mid-course correction.
- Overshoot
- Passing the target and having to come back.
- Undershoot
- Stopping short and having to push on.
- Micro-correction
- The small adjustment after a flick; good players need less of it.
Flick test questions
I overshoot right but undershoot left. Why?
Asymmetry is common and usually comes from grip or arm position, not the mouse.
Do I have to hit the target?
Hits are counted but the overshoot measurement works even on misses.
Is this the same as the aim test?
No. The aim test measures precision at rest; this measures the flick itself.
Fix a flick problem
Constant overshoot
Lower sensitivity 10 to 15 percent and rerun.
Constant undershoot
Raise sensitivity slightly, or use more arm on long flicks.
Erratic results
Run the polling and jitter tests; hardware instability shows up as inconsistency here.