Device Bench

Device test · Input

Click Speed Test

Choose a time window, then click or tap the pad as quickly as you can. Your first click starts the timer and counts toward your score. Watch your clicks per second (CPS) as you go, then use Reset for another run. Counting and timing happen in your browser; nothing is sent anywhere.

Window5 s Time left5.0 Clicks0 CPS0.0 Session best—

How this test works

Choose a 1, 5, 10, 30, or 60 second window. The first activation of the pad both adds a click and starts the timer, so there is no separate start signal to react to. During a run, CPS is the count divided by elapsed time; the final score is the count divided by the selected window length, shown to one decimal place. Reset clears the current run, and changing the window starts you over too. Neither clears Session best.

The page normally counts a primary-button press or touch contact when it receives pointerdown, rather than waiting for a completed click. It ignores the trailing pointer-generated click event to avoid counting the same press again. Keyboard activations count through click events with detail set to 0. In browsers without Pointer Events, it uses mousedown and touchstart instead. Timing comes from performance.now() when the page handles an activation, not from adding up screen refreshes. A delayed display update does not extend the window: an activation handled at or after the cutoff is discarded.

Your score reflects the events this page receives, not a direct count of physical finger movements. Device processing, the operating system, and browser scheduling can affect which events arrive and when, so use the same device, browser, input method, and window length when comparing runs. Extra events can raise the count, but a high score alone cannot tell you whether they came from your technique, software, or a faulty switch. It does not measure click latency, the delay between a physical press and its registration; the page has no timestamp for the physical press to compare against.

Frequently asked questions

What counts as a good CPS score?
Compare your score with a few of your own runs on the same setup and window length. This page has no population benchmark or leaderboard. If you change your device or switch from mouse clicks to taps, start a separate comparison. CPS tells you how many pad activations were counted per second, not how good your reflexes are.
Why can my 1 second and 60 second scores differ?
One second captures a short burst; 60 seconds asks you to keep going for a minute. Your pace may change as you settle into a rhythm or tire. Each counted activation also has more weight in the shorter window because the final count is divided by fewer seconds. Compare like with like: a 1 second run against another 1 second run, not a 60 second run.
Does my mouse change the result?
Yes, but the score does not isolate the mouse from the rest of your setup. It counts accepted events, including any extra ones that reach the page. If slow, deliberate clicks produce unexpected counts, compare another mouse in the same browser or use the mouse test to inspect the intervals. That can help you investigate; it does not identify a worn switch by itself.
Can I take the test on a phone or tablet?
Yes. Tap the pad to start, then keep tapping until time runs out. The timer and CPS calculation are the same as for mouse clicks. Using several fingers changes the input, and older browsers may group new contacts into one event. Keep touch scores separate from mouse scores and use the same tapping method each time.
Is my score recorded or uploaded anywhere?
No. Counting and timing run in this page, and your score is never transmitted. There are no accounts or leaderboards. Session best is the highest CPS from any completed run in this tab, across all window lengths. It is kept in page memory only. Reset and window changes leave it intact; closing or reloading the tab clears it. Write down any scores you want to keep.

Related tools