CPS and clicks per second explained
CPS stands for clicks per second, and the final number depends entirely on the time window chosen for the measurement. This page explains the exact math behind the result, how the counter registers every click, and the real reason a speed ceiling exists that has nothing to do with the counting code.
The final calculation uses toFixed(2), so the result always shows two decimal places, even when the division lands on a whole number.
In the 1-second window, each individual click carries more weight in the final result: one extra or missing click shifts the CPS by a whole unit.
The live CPS uses only the time already elapsed and rounds to 1 decimal place, a provisional value that changes every frame until the round ends and the final result is calculated with 2 decimals.
CPS stands for "clicks per second". It's the average of how many times you click in one second, calculated by dividing total clicks by the test duration.
It is the total number of clicks registered during the round divided by the chosen duration in seconds, rounded to 2 decimal places. A round of 30 clicks in 10 seconds closes at exactly 3.00 CPS.
It counts per event: every click the browser delivers to the button adds 1 to the counter immediately. The per-frame redraw (requestAnimationFrame) only updates the visual countdown on screen, with no relation to how many clicks were counted.
Because the ceiling comes from the mouse, the trackpad and the operating system, not from the counting code. Devices have their own sampling rate, and many systems filter repeated clicks under a minimum time window, treating them as hardware noise.
No, the best CPS is stored separately per duration, in a map indexed by the chosen seconds. Your record in the 5-second window does not touch the record in the 60-second window, each one keeps its own value.