Jitter Click Test: Compare Short CPS Runs

Compare your chosen method under the same conditions

1. Choose one duration. Use 5 seconds for a short sample or 10 seconds for a longer window. Keep that choice unchanged while comparing attempts.
2. Record an ordinary-click baseline. Run one sample with your usual clicking method on the same mouse and browser. Note its count and Final CPS, then select Reset.
3. Test your chosen jitter-clicking method. Keep the pointer inside the pad and use the same primary mouse button throughout. Avoid touch, keyboard activation or an external clicker if the comparison is meant to be manual mouse input.
4. Repeat and record. After each complete run, note the count and Final CPS before selecting Reset. Three runs can show how your results differ; the widget does not store or summarize those runs for you.

The page counts events, not a technique. Its score does not establish how you moved your hand or whether you used manual input. The useful comparison is between complete samples taken under conditions you have kept consistent.

Read several results instead of only the best one

In this example, the best score is 8.20 CPS and the lowest is 7.20 CPS: a 1.00 CPS range between runs. That range describes three whole-run scores. It is not the variation between individual click intervals, and the widget does not calculate it automatically.

Compare the same duration before drawing a conclusion. A five-second burst and a ten-second run include different amounts of activity and idle time. Record pauses or a missed target so that an interrupted attempt is not treated as an equivalent sample.

There is no built-in good, expert or world-record category. These numbers describe events received by this browser, not a maximum for your mouse or a prediction of what another app will accept.

What the timer and CPS values include

• First click: starts the timer and is included in the count.
• Deadline: clicks exactly at or after the selected duration ends are excluded.
• Final CPS: count divided by the full 5 or 10 seconds, including idle time if you stop clicking early.
• Current CPS: count divided by elapsed time while running. The early value can jump because very little time has passed.
• Reset: ends and clears the current measurement while keeping the chosen duration. A finished test needs Reset before another run; changing the duration between runs also clears the old result.

The duration control is locked during a run. Keep this tab visible: hiding or leaving it cancels the measurement and clears its partial result. Return and select Reset to start again.

Equivalent interval is a conversion

The result’s Equivalent interval is 1000 ÷ Final CPS, displayed to two decimal places in milliseconds. At 8 CPS, that is 125.00 ms for an evenly spaced pace. It does not reveal your actual click gaps or instruct another app to use that speed. For arbitrary values, use the click interval calculator; for measured gaps, use the auto clicker speed test.

Check the input before comparing a low or high result

Reset and make one ordinary click in the middle of the pad. If the count does not change, check the mouse-button test. If it does, keep the pointer on the target and repeat the same duration. A low count alone does not identify a mouse fault or establish why events were missed.

This pad counts primary click events. Right and middle clicks are excluded; use the right-click test for right-button CPS. Touch and keyboard activation of the button can also register, so keep them out of a mouse-only comparison. Simply moving the pointer or holding a mouse button does not create a stream of clicks.

Use the general CPS test for a 30-second window, or the tool directory to select a different measurement. The online A/B/C demo generates its own page events; this jitter test only counts arriving input and cannot click another page or desktop app.

Last reviewed: October 26, 2026