A clicks per second score is only as meaningful as its measurement window. Our CPS test offers four windows, 5, 10, 15, and 30 seconds, and the same hand produces very different scores across them. This article documents how the timer decides what counts, when it stops, and which of the two CPS numbers on screen you should believe.
When the clock starts, and what counts
The test has one button and three states, idle, running, done. Your first click does two jobs at once. It starts the timer and it counts as click number one. There is no separate start signal and no warmup click, so every score in the tool includes the click that launched it.
The clock reads Date.now at start, then a 50 millisecond interval recomputes the elapsed time and repaints the display. The stop check runs on those ticks. When a tick sees elapsed time at or beyond the window, the interval clears and the state flips to done.
The 50 millisecond tick has a consequence. Clicks that land between the true window end and the next tick still increment the counter, because the state has not flipped yet. Your score can absorb up to 50 milliseconds of extra clicking, which at 10 CPS is worth about half a click.
The two CPS numbers, live and final
While the test runs, the display divides clicks by elapsed time and shows one decimal. This live number is inflated at the start. One click against the first tick, near 0.05 seconds, can display as 20.0 CPS. The live figure settles as the window fills, and short windows never fully settle.
The final score uses a different divisor. At the end, the component divides total clicks by the chosen duration, 10 seconds by default, and prints two decimals. Sixty two clicks in a 10 second window shows as 6.20 CPS on the result card.
Believe the final number. The live counter exists to give your hand feedback, and its early spike says nothing about you.
The rank thresholds
Ranks come from a fixed table, checked against the final CPS with a greater than or equal comparison:
0 Turtle
4 Mouse
6 Human
8 Cheetah
10 Pro Gamer
13 Machine
15 GOD
The bands are uneven. The gap between Human and Cheetah is 2 CPS, and the gap between Machine and GOD is another 2. Crossing 6 into the Human band is the realistic ceiling for ordinary clicking on a normal mouse over 10 seconds. Scores well above 10 usually come from special clicking techniques rather than faster fingers.
Window length changes what a rank costs you. Forty five clicks in the 5 second window is 9 CPS and ranks Cheetah. The same pacing held for 30 seconds, 270 clicks, is still 9 CPS. Sustaining the rate is the hard part, which is why long windows separate practice from bursts.
The best score, and where it goes
The tool keeps a personal best in component state, rounded to two decimals, and shows it under the result with a best label. Each finished run compares against the stored value and the higher one survives.
That value lives in memory only. A reload wipes it, navigating away wipes it, and nothing is sent anywhere. There is no account, no leaderboard, and no storage. Treat the best line as a session streak, and record the number outside the tool when you want to track it across days.
Steps for a comparable run
1. Pick one window length and keep it for every run you compare. Ten seconds is the default and the common convention.
2. Use the same input device for every comparison. Mouse and trackpad scores do not mix.
3. Start from idle state each time, and let the result card appear before the next run.
4. Read the final two decimal score, and ignore the early live spike.
5. Record the score outside the tool, because the tool forgets your best on reload.
Checklist for a clean measurement
- The window is set before the first click, because changing it mid-run resets everything.
- The browser window has focus, since clicks outside the big button do not count.
- You clicked the button itself, the only counted target.
- The final score, not the live counter, is the number you write down.
- You remember the first click that started the timer is included in the total.
What a CPS number cannot tell you
The tool counts the click events it receives. It cannot see your mouse polling rate, your operating system double click setting, or how many events the browser merged between frames. Two people with identical hands can post different scores on different hardware. The number works as a self comparison over time on one device, and it fails as a comparison across devices.
Run a 10 second window on the
[CPS test](https://webrecast.com/en/cps-test) and write down the final score next to your
device. If your short window and long window scores sit far apart, that gap is the kind of
data we want to hear about.
