Rules & quick reference
| Input | Primary pointerdown events |
|---|---|
| Short-interval threshold | Less than 80 ms; heuristic only |
| Log | Most recent 20 intervals |
| Interpretation | Short interval does not establish a faulty switch |
Use slow isolated presses
Place the pointer over the panel and press the primary button once about every second. Watch the interval between one press and the next. The first press has no interval and establishes the timestamp. Every later press is compared with its predecessor using the same browser clock. A session count and short-interval count remain visible while the log keeps the most recent twenty entries. Select Save this session to add the summary to local history.
Why the threshold is only a clue
Two received presses less than eighty milliseconds apart are highlighted as a short interval. This threshold is a transparent heuristic, not a manufacturer specification or an electrical measurement. Intentional rapid clicking can easily produce such a pair. A contact bounce problem is more plausible when an extra press repeatedly appears after one slow deliberate action, but even that observation needs to be checked against software settings, macros and another application before attributing it to a switch.
What the browser actually receives
The test listens for initial primary presses rather than the high-level dblclick event, whose behavior depends on double-click settings. It measures delivery timing after the mouse, firmware, operating system and browser have processed input. Software or firmware debounce may suppress a repeat before it reaches the page. Conversely, synthetic input can appear as separate events. This panel cannot inspect raw switch voltage, mechanical wear or USB reports that never become pointer events.
Collect a reproducible example
Record the input device, connection mode, approximate click pace and whether an unintentional repeat occurs in other applications. Try a different port or another device only if you want to isolate a cause, changing one condition at a time. A clean session does not prove that an intermittent fault is absent. A high short-interval count while deliberately chasing CPS is expected and provides little diagnostic value. Use the CPS game for speed practice and reserve this tester for calm interval inspection.
Your result stays on this device
Completed game results are saved in this browser when local storage is available. Bests and recent history describe this device’s saved runs, not a public leaderboard. Changing browsers, clearing site data or using private browsing can remove them. Copy score writes only the visible result summary to your clipboard when you request it; sharing is your choice. Clear local game data removes scores, daily completion markers and the saved 2048 board for this origin. No game result is uploaded, and the games remain usable when persistent storage is unavailable. Use the rule table to check what the active mode measures before comparing another session. A changed duration, input method or grid difficulty can change the task even when the displayed score uses the same unit.
Frequently asked questions
Does a red interval prove a broken switch?
No. It flags a pair under 80 ms. Intentional fast presses, macros and software can also produce it.
Why not use dblclick?
That high-level event depends on click interpretation settings. This tool compares individual initial presses.
Can debounce hide a fault?
Yes. Firmware or software may suppress extra events before the browser receives them.
Are all click timestamps stored?
Only the visible recent log is held during the visit. Saving records a session summary locally.
Built by Mihai · Reviewed 2026-10-24 · Read the related technical guide · Testing policy