What it does
Useful, focused capabilities
- 1, 5, 10, 30, and 60 second modes
- Mouse, touch, and Spacebar input
- Average CPS and peak one-second burst
- Trusted-event counting and repeat-key rejection
- Optional local aggregate history
Skill & performance · browser-local
Clicks per second test
Run a private CPS test for mouse clicks or Spacebar presses with peak burst, consistency, multiple durations, and local-only history.
Work happens in the current browser. The route does not require an account or a server-side processing job.
Interactive browser workspace
Clicks per second test
The live tool is loaded in this browser only. This route does not need camera, microphone, or screen-capture permission for its main task.
Load the interactive workspace →Browser compatibility
Requirements and honest fallbacks
JavaScript and a modern browser; mouse, touch, or Spacebar input is required for a meaningful run.
- JavaScript
- pointer or keyboard input
- Local storage
Questions people ask
Clear answers and limits
What is a CPS test?
It measures how many trusted click or Spacebar events your browser receives per second during a fixed interval.
Why is my one-second score higher?
A one-second burst emphasizes a short peak. Longer modes reduce the effect of a brief burst and better reflect sustained input.
Does touch count?
Yes. Primary touch pointer events count in pointer mode, although touchscreens and mice should not be compared directly.
Can an auto-clicker inflate the result?
Browser-scripted synthetic events are ignored, but external automation can still generate trusted operating-system input. The tool is for personal practice, not anti-cheat certification.
Does right-click work?
Select the secondary button in settings. The context menu is suppressed only inside the test pad for that mode.
What this tool checks
Measure mouse, touch, or Spacebar input during a fixed CPS session. The page reports average clicks per second, peak one-second burst, duration, mode, and optional local aggregate history. Synthetic browser events are ignored, while external automation can still produce trusted operating-system input. Compare the same input device and duration for meaningful practice. Touch, mouse, and keyboard results are not interchangeable, and the score is not anti-cheat certification.
What to choose and what you get
What to choose
- trusted mouse, touch, or Spacebar events
Result
- an on-page click-rate result and a downloadable PNG result card
Supported use
- 1-, 5-, 10-, 30-, and 60-second click or Spacebar modes.
- Average CPS, peak one-second burst, trusted-event counting, and optional local aggregate history.
Before you start
- It does not detect or certify every external automation path.
Supported formats
- Accepted formats: keyboard, pointer, timing, browser state.
- Output formats: HTML report, PNG.
Browser support and permissions
- Modern browser with JavaScript; timing, scheduling, clipboard, and device behavior vary by browser.
- No camera, microphone, or screen permission is needed.
Choose the right settings
- Choose this route for mouse, touch, or Spacebar speed practice.
- Use /typing-speed-test for WPM and text accuracy.
- Use /keyboard-tester to inspect keys and event delivery.
Worked example
A five-second mouse-click session needs clicks-per-second, peak burst and consistency measured without remote storage.
Starting facts
- Only trusted pointer or Spacebar events are counted.
- Hardware, browser and operating-system scheduling affect results.
Observed operation: Choose the input mode and duration, complete the visible run and calculate the local event aggregates.
Review the result: Compare only repeated foreground runs under the same device and input settings and review consistency with the peak.
Boundary: The result is not anti-cheat proof, a hardware certification or directly comparable with tests using different event rules.
Choose another tool when
- A CPS score is a personal browser measurement, not anti-cheat evidence or a certified input benchmark.
If it does not work
- Synthetic browser events are ignored, so scripted dispatch does not raise the reported count.
- Touch, mouse, and Spacebar input can produce different event timing and should be compared separately.
- A blocked storage API prevents aggregate history from being retained.
Things to know
- CPS depends on the selected duration, input device, browser event delivery, and operating-system scheduling.
Privacy boundary
Browser interaction and local results stay in the current browser session and are not sent to an Aftermath processing service. How local processing is verified.
What this tool verifies
Reports average CPS, peak one-second burst, duration, input mode, and optional aggregate history from trusted browser events.
Check before sharing
The score describes trusted events received in this browser session; it does not certify hardware, automation absence, or competitive performance.