What a click speed test measures
A click speed test measures how many accepted pointer presses you make during a fixed time window. Testpartout reports that rate as clicks per second, or CPS. The result is a practical browser measurement of one simple task: repeated primary pointer presses under the same session rules.
It is not a universal gaming skill score. Clicking quickly can matter in some games and workflows, but game performance also depends on movement, timing, targeting, decision-making, hardware and software settings that this test does not measure.
The CPS formula
Testpartout computes:
CPS = accepted clicks / fixed test duration in seconds
In the current Click Speed Test, the duration is fixed at 10 seconds. A fixed duration keeps the denominator stable, so one run can be compared with another without a shorter session making the rate look artificially high.
How the 10-second session starts
The first valid pointerdown starts the session and also counts as click 1. This avoids measuring the time you spend reading the page or placing your hand. Once that first accepted press arrives, the clock starts and the same pointer modality is used for the rest of the run.
Why pointerdown is used
The press is the earliest clear signal that the pointer action happened. Waiting for release would add how long you kept the button or contact held down, which is not part of the click rate Testpartout is trying to measure.
Which inputs count
Click Speed is a pointer measurement. Testpartout accepts primary pointer presses from a mouse, touchscreen or pen. Right click, middle click, secondary touches, barrel-button style inputs and unknown pointer types are excluded.
Keyboard input does not count as CPS. Space and Enter can activate page controls where that is appropriate, but they are not counted as clicks in the measurement because keyboard repetition is a different input task from pointer clicking.
Why the input method is frozen
The first accepted press sets the session modality: mouse, touch or pen. Later presses from a different pointer type are ignored, so a result cannot mix hardware paths in one number. That keeps a mouse run, a touchscreen run and a pen run as separate practical measurements.
This does not mean one modality is universally better. Different devices have different sampling rates, ergonomics and browser event behaviour, so comparisons are most useful when you repeat the test with the same setup.
The deadline is authoritative
The session ends at 10 seconds of measured elapsed time. The engine clamps elapsed time so it can only move forwards, and a click at or after the deadline completes the run instead of adding another click. Late clicks cannot extend the session and cannot create an eleventh second of scoring time.
If the page stops being visible during a run, the session is cancelled rather than scored. A hidden or throttled tab is no longer a fair measurement environment, so Testpartout avoids saving a result from it.
Browser and input-device limits
The browser sees pointer events after the device, operating system and browser have all had a chance to process them. Mouse polling rate, touchscreen sampling, wireless latency, system load and event scheduling can all influence the number. The test records the browser event stream it receives; it cannot inspect the physical switch or touch sensor directly.
For that reason, treat CPS as a repeatable score for you on this device and input method. A personal best saved locally in your browser is more meaningful than a comparison against a different person using different hardware.
Reading the result
Testpartout shows clicks, CPS, elapsed time and the input method for the run. It does not show good or bad bands, averages, percentiles or gaming labels, because Testpartout has no real aggregated data to justify those claims.
Run the Click Speed Test several times under similar conditions if you want a useful comparison with yourself. The platform-wide rules for browser-based measurements are explained on the methodologypage.