Clicks Per Second Test

Read the result

Calculate clicks per second from a run

Divide the number of accepted target activations by the selected duration. If a five-second run records 32 clicks, the result is32 ÷ 5 = 6.4 CPS. This is an average across the whole test, not the fastest instant during it. Results are rounded to one decimal place.

The Start button begins the clock but does not add a target click. Only activations of the test target during the running interval count. Activations at or after the deadline are excluded, even if the browser has not yet drawn the finished screen.

That means moving from Start to the target uses some of your available time. This has a particularly large effect in one-second mode. Keep the same setup between attempts so you do not mistake a shorter movement for faster clicking.

Compare matching durations and controls

A one-second run captures a brief burst and is sensitive to its start. Five seconds gives more time to establish a rhythm. Ten and thirty seconds include more of your ability to maintain that rhythm. A higher result in the shortest mode does not predict the same pace over a longer run.

For example, 32 clicks in 5 seconds gives 6.4 CPS, while 58 clicks in 10 seconds gives 5.8 CPS. The longer run has more total clicks but a lower rate. Compare the rate only after noting the duration.

Mouse clicks, touchscreen taps, and keyboard activations all work here. Record which input you used; a keyboard run is not a measurement of mouse clicking speed. Switching device, input method, or technique changes the conditions of the comparison.

Build a useful personal baseline

1. Choose one duration and input method, and do one practice run.
2. Take three measured runs, resting between them.
3. Write down all three results instead of keeping only the highest.
4. Repeat the same setup another day to see whether the group of results changes.

For scores of 6.2, 6.4, and 7.8 CPS, the middle score is 6.4. Keeping it alongside the full set makes the unusually high run visible without letting it stand in for every attempt. These are example scores, not population benchmarks or targets you are expected to reach.

The test is a casual browser challenge. It does not certify gaming skill, hardware performance, or unassisted input. Keep practice comfortable and stop if it becomes uncomfortable. For responding to a signal rather than repeated activations, try the Reaction Time Test.