Click per second test

How it works

You start a short timer, press the same control as fast as you can, and stop when the window ends. The page records down-presses it actually received, then reports clicks per second, often written CPS. That is the whole arithmetic: count divided by duration. A longer window smooths a burst. A shorter window rewards a sprint. Compare runs only when the window is the same length. A five-second pace and a ten-second pace are different exams.

The input can be a mouse button, a trackpad click, a laptop key if the page allows it, or a tap on glass. Those are not the same event. A result from a phone and a result from a desktop mouse should not share a trophy line. Label the device on any note you keep. “CPS on this mouse, five-second window” is a complete sentence. “My click speed” is not.

This is a tool page, not a league with a hidden judge. There is no official world ranking on a random website. A screenshot of a number is not a credential. Use the test to compare your own runs, to see whether a new mouse feels slower, or to settle a friendly argument with the same device and the same window. Auto-clickers and bind macros measure software. If you came to measure a hand, leave those off.

Reading CPS instead of a vibe

CPS is a rate. Twenty clicks in four seconds is the same average pace as five clicks in one second. The raw click count without the duration is not a speed. Always read both. If the page also shows a peak burst, that peak is not the average across the whole window. Decide which figure you meant before you quote it. Quoting the peak as if it were the average is how a screenshot lies without changing a digit.

Buttons bounce. A cheap switch can register two clicks when you meant one, or drop a click when you meant two. A score that looks “too high” on one mouse and “too low” on another may be measuring the switch, not your tendon. Try the same window on a different pointer before you train for a number the hardware cannot hold. Fatigue is real: a fifth run in a row is often slower than the second, even if you “know the trick.” Space the trials.

Pick one pointer and one window length, and keep both for the comparison. Rest the heel of the hand; hovering wastes travel. Count only the clicks the page records, not the ones you felt. Throw away the first run spent finding the target.

Stop when the bell ends. Extra presses after the window are not in the score. Jitter on the page is a void run. If the pointer lags, you measured a busy tab, not a finger. Close the extra work and retry. A fair click per second test is boring on purpose: same button, same duration, same posture, then a number you can read without a story attached.

One finger, two fingers, and what not to mix

Some people butterfly or jitter two fingers on one button. Some people tap glass with a thumb. Those techniques change the count. They are allowed if everyone in the argument used the same one. They are cheating only if the rule was “one finger, one button” and you switched in silence. Write the rule on the note. Silence is how a kitchen contest becomes a grievance.

Clicks per second is a fraction. If you hide the seconds, you are showing a pile of clicks and calling it a race. Touchscreens report taps. Accessibility repeat keys fire extra events. A laggy remote desktop adds delay that your hand never felt. Each of those belongs in the label if it was in the run. The tool can only count what reached the page in the seconds you gave it. It cannot count the clicks you meant in your head.