Short answer: in a 60 or 100 second click test the average usually drops because every later, slower second is added to the same division. CPS is counted clicks divided by seconds, so once the pace falls below your running average, the average has to fall with it. The test counts the clicks; it cannot tell you whether the slowdown came from tiredness, technique, the device or something else. CPSKit’s longest run is 60 seconds, so a 100 second test cannot be run here.
What a longer test counts
The method does not change with length. The first click starts the run and counts as click one, the duration is a whole number of seconds from 1 to 60, and the result is counted clicks divided by that duration, with no smoothing. A click arriving at exactly the full duration is not counted. The CPS test page offers 1, 5, 10, 30 and 60 second presets and a custom duration from 1 to 60 seconds. There is no 100 second option, so the 100 second figures in this article are arithmetic on invented numbers, not something the tool can produce.
A longer window makes each click worth less. These values are arithmetic, rounded as shown:
| Test length | Value of one click | Available in CPSKit |
|---|---|---|
| 10 s | 0.100 CPS | Yes |
| 30 s | 0.033 CPS | Yes |
| 60 s | 0.017 CPS | Yes |
| 100 s | 0.010 CPS | No (maximum is 60 s) |
Why the average falls: a worked example
The following numbers are invented for illustration, not real data and not a benchmark. Suppose a run starts fast, settles, and then slows further. Clicks per second in each stretch:
| Stretch of the run | Clicks per second | Clicks in the stretch |
|---|---|---|
| Seconds 1–10 | 8 | 80 |
| Seconds 11–30 | 6 | 120 |
| Seconds 31–60 | 5 | 150 |
The same invented run gives a different CPS depending on the window you divide by:
| Window | Counted clicks | Clicks divided by seconds |
|---|---|---|
| First 10 seconds | 80 | 80 / 10 = 8.00 CPS |
| First 30 seconds | 200 | 200 / 30 = 6.67 CPS |
| Full 60 seconds | 350 | 350 / 60 = 5.83 CPS |
Nothing was lost between those rows; each is the same clicks divided by a longer window. Every added stretch ran at fewer clicks per second than the average so far, so the average moved down each time. If this invented run were stretched to 100 seconds with 40 more seconds at 4 clicks per second, it would count 160 more clicks: 510 clicks divided by 100 seconds is 5.10 CPS. The 100 second figure is lower again for the same reason, and it is not something you could measure on this site.
The rule that follows is plain arithmetic: adding seconds that are slower than the running average pulls the average down, and adding seconds that are faster pulls it up. A flat run keeps its average; a run that speeds up late would raise it. A falling figure therefore says the later seconds were slower than the earlier ones, which is exactly what the per-second chart shows.
Reading the per-second chart over 60 seconds
After a run, the full CPS test page shows a “Clicks in each second” bar chart. A 60 second run has sixty bars. Read it in blocks rather than bar by bar, because single seconds are noisy when each holds only a handful of clicks. A simple method:
- Note the result line first: clicks, duration and CPS for the whole run.
- Add up the bars for the first 10 seconds and the last 10 seconds and divide each by 10.
- Compare the two figures. The gap between them is how much the pace moved across the run.
- Look for where the bars change: a steady decline, a sudden step, or a recovery near the end.
The method is arithmetic on counted clicks. It does not say why the pace moved, only that it did and roughly when.
What the drop does not tell you
A falling pace has several possible explanations, and the test can separate none of them. Tiredness in the hand or finger is one. A change of grip or technique mid-run is another. A mouse button, a touchpad or a touch screen may respond differently as the run goes on. The test records only the events your browser reports; it has no sensor for muscle, grip or device wear. CPSKit has no dataset of real people running 60 second tests, so this article makes no claim about how large a typical drop is.
One cause is checkable. A switch that registers one press as two events inflates the count; at 60 seconds each extra counted event adds 0.017 CPS, so a few of them are hard to see in the total. If you suspect that, use the double-click test and follow the 60-second browser check for double-clicking. The open double-click input behavior dataset that sits beside this article documents how browsers report double-click-related events. It is not an endurance dataset and contains no 60 second click runs.
How to compare 60 second runs fairly
Keep the input type, device and duration the same. CPSKit counts only the chosen input type, keeping mouse, touch, pen and keyboard separate, so results from different inputs are not repeated measurements of one action. The following is a judgement, not a tested protocol:
- Pick 60 seconds and keep the same device and input type for every run.
- Do several runs with a proper rest between them, so each starts from a similar state.
- Sort the results and report the middle value, the median, next to the best.
- Keep 10 second and 60 second scores separate. They answer different questions.
Results are saved only on your device, with no account or leaderboard. For the comparison method, see how to track click speed over time and compare fairly. For short runs, read what a 10-second run tells you and why short bursts read higher. For interpreting any score, see how to read CPS scores and averages, and for practice advice read how to increase click speed. To choose a test for a different problem, see the full CPSKit toolbox.
Frequently asked questions
Why is my 60-second CPS lower than my 10-second CPS?
The longer run divides all its clicks by 60, including the slower seconds after the start. If your pace fell below the 10 second average, the 60 second average is lower. Both numbers are correct; they cover different windows.
Can I run a 100 second test on CPSKit?
No. Duration is limited to 1–60 seconds, and the 60 second preset is the longest. A 100 second result from another site is not comparable with a 60 second result here.
What does one extra click change in a 60-second test?
It adds 1/60, about 0.017 CPS. For example, 300 clicks over 60 seconds is 5.00 CPS, and 301 clicks is 5.02 CPS when rounded to two decimal places.
Does a drop mean I am getting tired?
It means the later seconds counted fewer clicks. The test cannot show whether the cause is tiredness, technique or the device, so treat the drop as a prompt to look at the chart rather than a diagnosis.
Does the first click count?
Yes. The first click starts the run and counts as click one. A click at exactly the full duration is excluded from the count.
These tools record real events observed in your browser. Results differ by browser, operating system and connection type, and a result does not certify the device or measure your hand beyond what the test page counts.