Independent browser benchmark
Run a clean five-round reaction drill, then switch to flick and tracking checks. Your browser keeps the run history locally so you can see what changes after a warm-up.
01 / performance lab
Choose a mode
Each mode measures a different part of the first-shot loop.
Click start, then click the stage as soon as it turns chartreuse.
02 / results
Use the median to compare runs. P95 and consistency show how often an outlier slows you down.
Finish one drill above to populate this panel with real browser measurements.
Trial trace
Exact values are also listed in the table below.
Read the result
A completed run will explain what this metric says and what it does not say.
| Date | Primary | Accuracy | Reference |
|---|
03 / how to read
A good warm-up is a controlled comparison. The useful question is not "what is the fastest number I can get?" but "what changed when I repeated the same task?"
Median is the middle observation after the run is sorted. It is less distracted by one unusually slow round, a missed flick or a momentary browser interruption, so it is the clearest number for your next practice comparison.
P95 shows the slow end of the run. If your median looks strong but P95 is much higher, the issue may be reset timing, hesitation or an inconsistent first move. Use the gap as a prompt to inspect the trace.
Standard deviation, hit accuracy and tracking stability describe control quality around the average. A fast reaction time with early clicks is not the same practice signal as a slightly slower run with no errors.
Before you run
Keep these conditions stable when comparing a CS2 click test, aim test or reaction test.
Use the same browser, display and pointer.
Close work that may steal focus or add frame drops.
Run two warm-up attempts before judging a change.
Compare median, P95 and errors together.
Example. If your reaction median improves but P95 and early clicks increase, you may be rushing. If flick accuracy rises while median stays stable, that is still a useful aim-training gain. The lab keeps both signals visible so the next decision is based on more than one headline number.
04 / protocol
The point is not a perfect number. It is a consistent baseline you can retest after changing sleep, warm-up, sensitivity or hardware.
Five random signals measure how quickly you respond after the visual change. Early clicks are recorded as errors.
Six targets appear at different positions. We track hit time, misses and the accuracy cost of rushing.
Hold your pointer over a moving target for ten seconds. Time on target and average error produce a stability readout.
Measurement note. This is a browser practice utility, not an official CS2 rating, anti-cheat diagnostic, medical measurement or population leaderboard. Keep the same device and browser when comparing runs.
05 / drill guide
The three modes answer different questions. Treat them as separate baselines instead of compressing every kind of aim practice into one score.
The CS2 reaction test isolates the visual-to-click loop. Randomized wait times make it harder to anticipate the signal, while early clicks remain visible as errors. Use this mode for first-shot response and warm-up comparisons.
The CS2 flick test adds spatial acquisition. A fast click only helps when it lands on the target, so median time and hit accuracy should be read together. This is the most useful mode for comparing speed against rushed misses.
The CS2 tracking test measures pointer time inside a moving target, average error and stability. It is a short control check, not a substitute for in-game crosshair placement, recoil control or a calibrated mouse input test.
A clean comparison session
Run the same browser-based protocol before and after a setting change. A useful comparison has a stable setup, enough repetitions and a note about what changed.
Warm up once without recording a conclusion.
Run Reaction, Flick or Tracking twice under the same conditions.
Compare the median, P95, accuracy and error count instead of the best round.
Repeat later if sleep, display refresh, sensitivity or browser focus changed.
Use the ledger as a practice journal. A lower median can be useful, but a narrower spread may matter more if your slow rounds are the problem. If a CS2 aim test improves only after repeated attempts, label that as a warm-up effect rather than a permanent skill change. The local history keeps the exact run values available so you can inspect that distinction.
06 / faq
There is no single official cutoff. Use the same setup for several runs and look at your median rather than one fast outlier. The reference bands in this prototype are guidance only and do not map to a FACEIT level or an in-game rank.
The reaction mode keeps the familiar color-change interaction, while Flick and Tracking add two aim-relevant checks. The result ledger also keeps median, P95, accuracy and local history together.
It includes the timing of your browser, display, operating system and input path, so it can reveal large setup changes. It is not a calibrated mouse-latency or monitor-latency instrument.
No account or upload is required. This MVP stores recent runs in your browser's local storage. Clearing site data or using a private window can remove them.
Press Space to start a test or respond during Reaction mode. Flick and Tracking are designed around pointer movement because they measure spatial control.
Do not compare their millisecond values as if they measured the same task. Reaction records a visual response, while Flick includes target location, pointer movement and click accuracy. Compare each mode with its own history and read speed beside errors.
A browser drill uses a screen, operating system, browser scheduler and pointer path that differ from an in-game frame pipeline. Use it to compare your own setup and warm-up state, not to predict a rank, aim score or exact in-game duel outcome.
Short, consistent sessions are more useful than constant retesting. One warm-up followed by two recorded runs is a reasonable starting protocol. Leave enough time between comparisons to avoid judging fatigue, anticipation or random variation as a settings improvement.