CS2 Reaction Time & APM Test: Counter-Strafing, AWP Peek & Spray Control
A CS2-locked APM test: per-key latency for W A S D, Shift, Ctrl, Space and both mouse buttons — find the key that costs you counter-strafes and AWP peeks. No download, no sign-up.
Ready, click to start
Overview
Most reaction tests stop at "click when it turns green". CS2 does not work that way. A duel is decided by which keys you press and how precisely — counter-strafing, the AWP peek, spray control: every one of them is a timing problem on the keyboard.
This page is the APM test locked to the CS2 key set: W A S D, Shift, Ctrl, Space and both mouse buttons — 9 inputs in total. What it measures is per-key latency (target key appears → you hit it correctly), with the slowest key marked in red. So the answer it gives is specific: are you slow overall, or is one particular key holding you back?
How to Use
- The key set is locked on this page: W A S D, Shift, Space and both mouse buttons (9 keys) — nothing from other schemes.
- Choose a run length: 5 / 10 / 30 / 60 seconds.
- Press Start and wait for the 3-2-1-GO countdown.
- Hit the highlighted key as fast as you can; a correct hit moves on immediately, and wrong presses still count toward your total actions.
- Read the scoreboard: APM, total actions, correct actions and accuracy.
- Read the key-latency line: every key's average time with the slowest one in red — that is your next drill target.
Feature Details
Counter-Strafing: Why Keyboard Timing Beats Mouse Speed
Stopping your momentum is barely about how fast you flick the mouse — it is about when and how precisely you release and counter-press the movement keys. You hold A to stop; you have to tap D at the right instant. Miss it by a few dozen milliseconds and the spray is already off.
- Per-key latency shows you which direction key is the problem: plenty of players are fine A→D and clearly slower D→A.
- The slowest key is marked in red. That is your first training priority — far more useful than adding hours blindly.
- Keys with fewer than 3 samples show their count (for example
Shift 120ms (1)) so you do not read one lucky press as a result.
AWP Peek and Spray Control: Reading Your Slowest Key
An AWP peek is a three-beat rhythm — stop, peek, fire: if the counter-strafe did not settle, the first shot after the scope goes wide. Spray control asks for the same thing, a stable pairing of keys and mouse rather than one burst.
- Use 5 / 10 seconds for reaction and precision, 30 / 60 seconds for consistency. The gap between the two run lengths is a signal in itself.
- Mouse buttons are tracked as their own keys — for many players the slowest "key" turns out to be one of them, and those are exactly scope and fire.
- History is accumulated per scheme, so your CS2 line never mixes with other schemes.
Want another subject? The Fortnite page drills build/edit key rhythm, the Overwatch page drills ability and movement keys — and the general APM test covers baseline RTS / MOBA speed.
Benchmarks
The table above is not a score standard — it is a key map: which of the keys measured on this page maps to which CS2 action, so "this key is slow" translates directly into "this kind of duel is lost". We deliberately do not quote community APM figures as a CS2 score line: CS2 itself does not show APM, which is exactly the gap this per-key latency view fills.
| Keys | CS2 action | Why its latency matters |
|---|---|---|
| W / A / S / D | Movement and counter-strafing | Stopping depends on when and how precisely you tap the opposite key — not on how fast you flick |
| Shift | Walk / silent movement | Walking early or late decides whether you give away or gain information |
| Ctrl | Crouch (duck) and crouch-spray | The timing of crouching decides duck-peeks and crouch-spray control |
| Space | Jumping, jump spots | The rhythm of window and box jumps is set by your takeoff timing |
| Mouse left | Primary fire / flicks | Whether the first shot after a peek comes out clean |
| Mouse right | Scope / secondary function | Every beat of the AWP peek — settle, scope, fire — lands on it |
Features
Use Cases
- Counter-strafe practice: find out whether your opposite movement keys respond as fast as you think they do.
- AWP peek warm-up: a few 10-second runs before you queue, so the peek-scope-fire rhythm is ready.
- Spray control check: hold accuracy above 95% while keeping pace — if accuracy drops as APM rises, you are rushing.
- Rebinding decisions: if Shift or Space is consistently red, that is a rebind conversation, not a practice problem.
- Cross-game baseline: run an RTS or MOBA scheme on Keyboard APM Test to compare raw speed with CS2-specific timing.
FAQ
Why does a CS2 player need an APM test?
CS2 is decided in milliseconds: flicks, counter-strafes and quick switches all live or die on precise key presses. This tool reports the response latency of each key separately, so you can tell "I am slow" apart from "this key is slow" — two different problems with two different fixes. Benefit: stop grinding blindly and fix the actual cause.
Does this train my counter-strafing?
It measures the keys counter-strafing depends on (the opposite movement keys, Shift) and marks the slowest one in red; the rhythm itself is trained in-game. To be precise: latency is recorded per key — this tool does not record the interval between two different keys, so it tells you which key is costing you, not how fast your counter-strafe combo is.
Can I find keys that stick, like Shift or Space?
Yes. Per-key latency and the sample count are shown directly (anything under 3 samples is marked with its count). Use that to decide whether to rebind keys in the game — this page always uses the CS2 key set, so the keys themselves are not editable here.
How is this different from a click-based reaction test?
A click-based test only measures "see target, click mouse". This one measures per-key response on the CS2 key set (W A S D, Shift, Ctrl, Space, both mouse buttons) and accumulates history per scheme, so the numbers map to the keys you actually press.
What do I do with the results?
Three steps: ① drill the red key first — it is your current bottleneck; ② use 5 / 10 seconds for reaction and 30 / 60 seconds for consistency; ③ go back into the game and check whether your counter-strafes and peeks feel steadier. For a baseline, run a RTS / MOBA scheme on the general APM test.