How it works
Your first click starts the clock and counts as click 1. From then on, every pointer-down event on the click area is counted until the time is up. The result is total clicks divided by the length of the preset, so a 5 second run with 40 clicks is 8.00 clicks per second.
Keyboard presses are not counted, and a keyboard user can focus the click area but cannot score with it. Taps on a touch screen are counted the same way and are saved separately from mouse runs.
When the run ends you get the headline CPS, the total number of clicks, a cumulative graph of clicks over time, and one audit line: the shortest interval between two counted clicks and how many intervals were under 20 ms. Escape cancels a run without saving it. A run is also cancelled if the browser tab is hidden.
Counting rules
- Only the primary mouse button counts. Right and middle button presses are ignored.
- A click is counted on pointer-down, not on release.
- There is no debounce: every pointer-down event the browser delivers is counted.
- The first counted click starts the clock. The deadline is that click plus the preset length.
- A press at or after the deadline is ignored and ends the run.
- Intervals under 20 ms are reported in the audit line, and those clicks are still counted.
- If you start with a mouse, only mouse presses count for that run. Touch and pen are likewise kept apart.
- Timing uses the timestamps the browser attaches to each event, not the moment the page handled it.
1 second versus 10 seconds
A 1 second run is a burst. The first click starts the clock and counts, so the starting click is a noticeable share of a very short run, and there is no time to settle into a rhythm. A 10 second run is about stamina and consistency: fatigue can show up, and the cumulative graph can bend over as the run goes on.
People often use different techniques for the two, and a fast 1 second score rarely predicts a 10 second score. That is why each preset is its own record: personal bests are only compared against the same duration, the same input type and the same rules version.
Comparing scores
Scores from different places are hard to compare. Clicking techniques such as jitter clicking and drag clicking can produce very high counts and are not equally available to everyone. Automation and macros produce numbers that look like clicking but are not. Without a controlled setup, a score on its own does not show who is faster.
Counters on other sites often disagree with this one because their counting rules differ. Some count on release, some start the clock on a separate button, some ignore very fast repeat clicks, and some round differently. A fair comparison needs the same device, the same duration and the same counting rules.
What this page does not do
It does not diagnose switches, double-clicking or any other hardware fault. A short interval is reported as a number, not judged. Very short intervals can come from technique, from the mouse, or from the browser. The audit line is there so you or a referee can see the evidence, and what it means is up to you.
Results are saved only in this browser, with no account. You can clear that history from the progress page.
Frequently asked questions
Does the first click count?
Yes. It starts the clock and is click 1, so a 5 second run counts clicks from time zero until 5 seconds later.
Why is my score different on another click speed test?
Different counting rules. Check whether the other site counts on pointer-down or release, whether the first click is counted, and how it handles clicks near the deadline. The rules for this page are listed above.
Can I use a touch screen or a trackpad?
Yes. Touch taps count, and are saved as touch runs, separate from mouse runs. A trackpad reports as a mouse, and its tap-to-click is counted like any other press.
What do I do if my score looks too high or too low?
Run it again with the same duration. A single run varies a lot, and the cumulative graph shows whether you started fast, faded, or held a steady pace. This page does not correct or adjust your score.