Device test · Input
Click Speed Test
Pick a window, then hit the pad as fast as you can — the clock starts on your first click, your clicks per second update live, and a session best is kept while the tab stays open. Every click is counted by this page in your browser; nothing is sent anywhere.
How this test works
The test measures your click rate: how many times you can activate the pad inside a fixed window of 1, 5, 10, 30, or 60 seconds. Nothing starts until your first click — that click is counted and starts the clock in the same instant, so no reaction delay is charged against you. When the window closes, your score is clicks divided by the window length, reported as clicks per second (CPS) to one decimal. The short windows describe burst speed; the long ones describe how well you hold a rhythm as your hand tires.
Each press registers on the pointerdown event — the instant your button or finger goes down — rather than on the completed click, and the click event that trails the same press is deliberately ignored so touch screens are never counted twice. Activating the pad from the keyboard still counts, because a keyboard activation arrives as a click with no pointer attached. Timing uses performance.now(), the browser's monotonic sub-millisecond clock: the page records the timestamp of your first click and derives the time remaining from it on every display update, so the window is always exactly the advertised length even if the display stutters. A press that arrives after the window has closed is discarded, not counted.
The result measures you plus your hardware, not either alone. Every click passes through the mouse's switch debounce, its USB polling interval, and the operating system's event queue before this page sees it, which adds a few milliseconds of jitter per click — negligible across a 10 second score, but enough that two machines can grade identical clicking slightly differently. The test also cannot tell technique from fault: a chattering switch that double-clicks inflates the count exactly like deliberate jitter clicking. And it does not measure click latency — the delay between pressing the button and the click registering — which is a different quantity this counter has no reference point to compute.