Skip to the click pad
ClickCPS

1 Second Click Test

One second, one burst, and a score that is simply your click count. The pad below is preset to a one-second run: the clock starts on your first click and stops exactly 1,000 milliseconds later, so eleven clicks is 11.00 CPS and nothing in between is possible.

Length
0.0s elapsed1.0s left
CPS
0.00
clicks
0
CPM
0
Band
—

The shortest test has the coarsest score

Every click test trades resolution against effort. The longer the run, the more clicks go into the average, and the smaller the effect any single click has on the result. Over one second that effect is at its maximum: one click is one whole point of CPS. Put differently, the one-second test cannot produce a score between 8 and 9, so anybody whose true burst rate sits at 8.4 will score 8 on some runs and 9 on others and will never see the number that describes them.

That is not a flaw to be fixed, it is the arithmetic of dividing by one. But it does change how the result should be read. A single one-second run is a coin-flip-grade measurement. Five of them is a range. The table below puts a number on exactly how coarse each run length is, which is the most useful thing to know before choosing one.

What a single extra click is worth at each run length. CPS per click is 1 ÷ length; CPM per click is 60 ÷ length. Computed by this site's scoring code and asserted row by row in its test suite.
Run length One click is worth (CPS) One click is worth (CPM) Clicks needed for 10.00 CPS
1 second 1 60 10
2 seconds 0.5 30 20
5 seconds 0.2 12 50
10 seconds 0.1 6 100
15 seconds 0.0667 4 150
30 seconds 0.0333 2 300
60 seconds 0.0167 1 600
100 seconds 0.01 0.6 1,000

Two rows are worth pausing on. At sixty seconds, one click is worth exactly 1 CPM — a neat coincidence of the units that makes the 60-second test unusually easy to reason about while you are running it. At one hundred seconds, one click is worth 0.01 CPS, which is precisely the last digit the display shows: the 100-second test is the only length here where one click moves the last printed digit by exactly one, and so the only length where every two-decimal score is reachable. The longer lengths in between do use their second decimal — a click over sixty seconds is worth 0.0167 CPS — but in steps that skip most of the two-decimal values, so the digit moves without being able to land anywhere.

Every score a one-second run can produce

Because the score is the click count, the whole result space of this test fits in one short table. There is no interpolation and no hidden precision — your run lands on exactly one of these rows.

The complete result space of a one-second run. CPM is CPS × 60. Band names are this site's own published scale (defined on the main page), not a comparison against other people.
Clicks in the second CPS CPM ClickCPS band
1 1.00 60 Warm-up
2 2.00 120 Warm-up
3 3.00 180 Steady
4 4.00 240 Steady
5 5.00 300 Quick
6 6.00 360 Quick
7 7.00 420 Fast
8 8.00 480 Fast
9 9.00 540 Rapid
10 10.00 600 Rapid
11 11.00 660 Rapid
12 12.00 720 Overdrive
13 13.00 780 Overdrive
14 14.00 840 Overdrive
15 15.00 900 Overdrive

Notice how few rows there are. Between the bottom of one band and the bottom of the next sits one or two clicks. That is another way of saying that on this length, a band change is not necessarily an improvement — it can be the same hand having a slightly better second.

The first click is free, and why that matters

A lot of click tests start a countdown and then measure what you do inside it, which means your reaction to the countdown is part of your score. Over ten seconds that costs you a fraction of a percent. Over one second it could cost a fifth of your result, and the number would be describing your reflexes as much as your clicking.

This test avoids that entirely: nothing happens until you click, and the click that starts the clock is counted. So the run is "your first click, plus everything you manage in the next second". If you click ten times, the tenth arrives at most one second after the first, and your score is 10.00 CPS. The alternative convention — measuring the gaps between clicks and dividing by nine — would score the identical run as 9 CPS. Both are defensible; this site uses the first one and states it plainly so you know what you are comparing against.

How to run a one-second test properly

  1. Warm up for thirty seconds first. Cold hands are slow hands, and the first attempt of a session is almost always the worst one. Do a few practice bursts you do not count.
  2. Start already moving. The clock waits for you, so there is no penalty for beginning your finger motion before the first click lands.
  3. Do five runs, not one. Write down the click counts. The spread between your best and worst is the honest description of your rate.
  4. Ignore single-run improvements. On this length, a one-click gain is inside the noise. Two clicks, repeatedly, is a real change.
  5. Stop before your hand complains. A one-second run is short, but repeating twenty of them back to back is not. Nothing here is worth a sore wrist.

When a one-second result is the wrong tool

If you want to know whether a mouse button registers reliably, this length is too short to show it — you need enough clicks for a discrepancy to be visible, which the 5-second test gives you at a fifth of the effort of a long run. If you want to know whether you can hold a rate under fatigue, one second contains no fatigue at all; that is what the 60-second test is for. And if the thing you are actually testing is a keyboard, the spacebar click test uses the same scoring with the space key as the input.

What a one-second run is genuinely good for: comparing techniques, comparing two mice back to back, and warming up before a longer attempt. It is the fastest possible answer to "can my hand physically go this fast", and it costs a second to find out.

Questions people ask

01 Why is my one-second score always a whole number?
Because the score is your click count divided by one, and you cannot click a fraction of a time. Nine clicks is 9.00 CPS exactly. There is no arrangement of nine clicks inside that second that produces 9.4 or 8.7 — the only way to move the number is to land a tenth click before the second is up.
02 Does the first click waste part of my second?
No, and this is the one genuinely generous thing about the format. The clock starts on your first click, and that click is counted. So the first click costs you zero elapsed time, and the remaining clicks have the full second to arrive in. That is why the score equals the click count rather than the click count minus one.
03 My score jumped from 7 to 9 between runs. Which one is real?
Neither, on their own. On a one-second run a single click is a whole point of CPS, so ordinary hand-to-hand variation shows up as a swing that looks dramatic. Run it five times and look at the range. If your results are 7, 8, 8, 9, 8 then your honest answer is "around eight, give or take one" — and the 10-second test will give you a finer-grained version of the same number.
04 Is one second long enough for jitter or butterfly clicking?
A one-second window is the format those techniques suit best, because neither has to be sustained — fatigue barely exists inside a single second. That also makes it the length where a technique flatters you most, and the length where a result transfers least to anything you actually do in a game. The mechanics of each technique are described on the main click speed test page.
05 How accurate is the timing over such a short window?
The window is measured with performance.now() and runs from your first click to exactly one second later, with clicks accepted only while the elapsed time is strictly under 1,000 ms. That boundary is precise to well under a millisecond. The imprecision on a one-second test is not in the clock — it is in the scoring resolution, which is a full 1.00 CPS per click, roughly a thousand times coarser than the timing.
06 What is a fair way to compare two mice on a one-second test?
Alternate them. Five runs on mouse A, five on mouse B, then five more on A — the alternation cancels out the warm-up effect that would otherwise flatter whichever one you tested second. Compare the raw click counts, and only believe a difference that shows up as at least two clicks consistently.

Related tools we built