Speed & Input Tests

CPS Test

Measure clicks per second with a focused browser-local test: choose duration and input mode, inspect live pacing and peak speed, compare halves and consistency, run a five-round burst set, and keep compact personal bests without an account.

1–300 second testsburst, standard, endurance, or custom duration

First-click startreaction time is not charged to the benchmark

Peak + consistencyinspect one-second buckets, not only average CPS

Comparable local historysame-duration, same-input personal bests

Wave180 · repeat-use click-speed studio

CPS Test — speed, pacing & repeatability

Run a clean first-input-start benchmark, compare mouse/touch/spacebar modes, inspect live pacing and peak speed, then repeat under the same setup instead of relying on a single lucky burst.

browser-local · no account

DurationInput modeTest type

0Actions

0.00Live rate

0Peak sliding 1s

—Pacing consistency

—Median interval

—1st / 2nd half

5.0Seconds left

—Comparable best

End tone

Quarter-second pacing trace

Peak uses a sliding one-second window rather than fixed second buckets. The trace uses 250 ms buckets so short bursts and fade are easier to see.

Best-of-5 rounds

Single · Best-of-5 is restricted to five 1-second rounds so each round measures the same short burst.

Recent browser-local runs

What to compare

Same duration1s burst and 60s endurance are different tests.

Same inputMouse CPS, touch TPS and spacebar KPS are not interchangeable.

Peak + averagePeak catches your best one-second burst; average covers the whole run.

Half ratesFirst-vs-second-half shows whether pace rose or fell in this run.

No fabricated global percentile or leaderboard is shown. Local bests are bucketed by duration, input mode and test type. Browser timing cannot prove technique, hardware debounce, macros, game skill or medical fitness.

Ready.

How to get a CPS result that is actually comparable

First input starts and counts

The timer does not charge reaction time before the first accepted action. That first action also counts toward the result, which keeps repeated runs consistent.

Choose duration for the thing you want to measure

One second emphasizes burst speed and is noisy. Five or ten seconds is easier to repeat. Thirty to one hundred seconds adds sustained pacing. Compare the same duration, not unlike tests.

Peak is not the same as final CPS

Final rate is all accepted actions divided by the configured duration. Peak is the busiest sliding one-second window. A short burst can be high even when the whole-run average is lower.

Mouse, touch and spacebar stay separate

Different hardware and browser event paths behave differently. The tool labels touch/pen as TPS and Space as KPS rather than pretending they are identical to mouse CPS.

Best-of-5 is for repeatability

Five one-second rounds show how repeatable a burst score is. Use the average and spread instead of treating one unusually good round as your normal speed.

History is compact and local

Recent results and personal bests stay in this browser. Raw pointer coordinates and full raw timestamp arrays are not saved. Clear the history whenever you want.

Challenge links do not upload history

A challenge link carries only the selected duration, input mode and target score. It does not include your saved history or raw click timing.

Comfort matters more than chasing an extreme score

Rapid repetitive clicking can be uncomfortable. Use a relaxed setup and stop if your hand or wrist hurts; this page is a browser benchmark, not a reason to push through pain.

Keep duration and pointer button with the score

CPS is only comparable when the test duration and pointer-button rule match. Median click interval adds a second view of clicking rhythm.

Local run history

Save up to five recent runs in this browser, repeat the same setup, clear the history at any time, and avoid treating browser timing as hardware-latency or medical measurement.