Mouse Click & Double-Click Test
Click each mouse button and watch it light up. The test shows which of the five buttons the browser receives, counts presses per button, and flags pairs of clicks on the same button within 50 ms as "possible bounce" — with the interval list. It does not declare a fault. Runs locally, no data leaves your device.
Nothing you click leaves this tab. No storage, no network requests. Refresh clears the session.
Possible bounce
Click buttons above to test for bounce.
Rapid double activation may be switch bounce, software double-clicking, or a macro. A browser cannot tell which — this is not a fault verdict.
What this measures
- Which of the five buttons (left, right, middle, back, forward) the browser receives on press and release.
- Per-button press counts for the current session.
- Time between consecutive same-button clicks, with pairs under 50 ms listed as "possible bounce" including their intervals in milliseconds.
What this cannot measure
- Switch debounce quality inside the mouse.
- Remapped buttons' original assignment — the browser sees only the remapped output.
- Macros or software-generated clicks versus hardware clicks.
- Whether possible bounce is a hardware fault — only vendor tools or another computer can narrow that down.
How to get a steady reading
- Click each of the five buttons once to confirm registration.
- Click normally to test how the switches feel.
- Deliberately double-click fast on each button to exercise the switch and see possible-bounce detection.
- Try the middle, back, and forward buttons too — some browsers or OS settings intercept back/forward for navigation.
- Compare on another computer before concluding a fault.
How to read the results
| Metric | What it means |
|---|---|
| Buttons | Which of the five buttons registered at least once this session. |
| Press count per button | Total button-press events the browser received for each button. |
| Possible bounce pairs | Count of same-button click pairs under 50 ms, with the interval list in milliseconds. |
| Interpretation | Possible bounce means rapid double activation — may be switch bounce, software double-click setting, or a macro. The browser cannot tell which. Do not treat it as a fault verdict. |
What "possible bounce" means
When the same button registers two clicks within 50 milliseconds, the test lists that pair as "possible bounce" and shows the interval. This pattern can come from a mechanical switch bouncing, a software double-click speed set too low, a macro sending two clicks, or the OS generating a double-click from a single press. The browser cannot distinguish these causes. Per the site's measurement honesty rule, the test reports the pattern without calling it a fault. Use another computer or vendor software to isolate the source.
Why the browser sees remapped output
If you remap buttons in vendor software (such as G HUB, Razer Synapse, or SteelSeries GG) or in the OS, the browser receives the remapped code. The test shows what arrived at the page. If you swapped left and right, the test will light "right" when you press the physical left button. That is not an error — it is the browser honestly reporting what it received.
Testing the middle, back, and forward buttons honestly
Some browsers and OS settings intercept the back and forward buttons for navigation (history back/forward). If those buttons do not light up in the test, a browser setting may be consuming the events before they reach the page. That is a finding about delivery, not about the mouse. The middle button (often the scroll wheel click) usually registers, but some mice or drivers treat it as a system gesture. The test reports what the browser delivers — if it does not arrive, the page never saw it.
Privacy
This test runs entirely in your browser tab. No click data is sent anywhere. No history is stored. Refreshing the page clears the session. You can verify this in DevTools: open the Network tab, click buttons, and confirm no requests fire.
Frequently asked questions
Does this test detect a failing switch?
It shows possible bounce — pairs of clicks on the same button within 50 ms, with their intervals. It does not diagnose a fault. A switch bounce, a software double-click setting, or a macro can all produce the same pattern. Test the same mouse on another computer to narrow the cause.
Why doesn't my back/forward button register?
Many browsers intercept the back and forward buttons for history navigation. If the test does not light up for those buttons, the browser likely consumed the event before it reached the page. Check your browser settings or try a different browser. That is a delivery finding, not a mouse fault.
What counts as possible bounce?
Two clicks on the same button within 50 milliseconds. The test lists each pair with its exact interval in milliseconds. The 50 ms threshold is a heuristic — not a standard — chosen to catch rapid double activations that feel like a double-click when you intended a single click.
Can I test mouse double-click speed here?
Yes. Click as fast as you can on a button. Pairs under 50 ms show as possible bounce with their intervals. This lets you see how fast you can physically double-click and whether the switch produces extra activations at that speed.
Does it store my clicks?
No. The session lives only in this tab. No data is written to localStorage, sent to a server, or logged. Refresh the page and the session is gone. You can verify this in DevTools: open the Network tab, click buttons, and watch — no requests.
Related tests
Mouse Polling Rate Test
Live Hz, stability graph, and variation — browser-observed, not a hardware measurement.
Mouse Tests Hub
Overview of all mouse tests: polling rate, click/double-click, and scroll.
Mouse Drift Test
Counts movement events reported while the mouse is untouched over 15 seconds.
Mouse Scroll Test
Wheel direction, step count per event, totals, and deltaMode unit — compare like with like.
Last reviewed 2026-10-12