Last event
—
Mouse click test online
A mouse click test checks whether every button registers exactly one press. Click left, right, middle, back, and forward on the live diagram — each region lights up with its own counter — then use the interval log to catch missed clicks and switch chatter.
Button
—
Since last
—
Left 0
Middle 0
Right 0
Back 0
Forward 0
Click each button on the diagram — every press lights up and counts
Button registration test — one press, one count
A healthy switch sends exactly one press event per physical click. This instrument counts pointer-button events per button id (0 left, 1 middle, 2 right, 3 back, 4 forward) and timestamps consecutive presses so bounce shows up as implausibly short intervals — the same quick check repair techs run before opening a mouse.
One press, one count
The ~80 ms chatter line
Button ids 0–4
Intermittent vs dead
When to use this test
Left and right click check
- Click left, then right — each counter should climb by exactly one per press
- A press with no count means a dead switch or a missed USB report
- Two counts from one press means the switch is bouncing
Recommended Reset and run ten slow presses per button for a reliable sample.
Middle click and side buttons
- Press the wheel straight down for middle click, then back and forward
- Side buttons that work once then die usually mean a worn microswitch
- No response at all can also mean the OS remapped the button
Recommended Test side buttons twice — intermittent faults hide on a single press.
Double-click chatter detection
- Deliberate double-clicks land around 100–250 ms
- Random intervals under ~80 ms mean the switch fires twice per press
- Normal single clicks show wide, irregular gaps with no chatter flags
Recommended Screenshot the log as RMA proof before replacing the mouse.
Before a return or warranty claim
- Capture counters after a fixed set of presses per button
- Pair with the interval log showing sub-80 ms bounce
- Note OS, browser, and mouse model alongside the screenshots
Recommended Keep both screenshots — counts prove dead buttons, the log proves chatter.
How to run a mouse click test
Three passes: every button once, side buttons again, then the chatter pad. Under two minutes.
-
Click every button once
Press left, right, middle, back, and forward on the diagram. Each region should flash and its counter should climb by exactly one.
Press slowly — fast mashing hides which press went missing.
-
Re-test the side buttons
Back and forward microswitches wear faster and fail intermittently. Give each ten more deliberate presses and watch for presses that add nothing.
Side buttons that die mid-session often recover after a rest — still a failing switch.
-
Check the interval log
Double-click the chatter pad several times, then single-click slowly. Random sub-80 ms intervals on single presses confirm switch bounce.
Screenshot counters plus log together — that pair is your RMA evidence.
Tips for a trustworthy click test
-
Test on the machine you actually use — USB hubs and KVM switches can swallow presses.
-
Disable macros and rapid-fire profiles in your mouse software before testing registration.
-
Keep the browser tab focused; background tabs may coalesce or delay pointer events.
-
Compare against a known-good mouse on the same port to separate mouse faults from PC faults.
Mouse click test online FAQs
What is a mouse click test?
A mouse click test verifies that each mouse button registers correctly when pressed. This page counts left, right, middle, back, and forward clicks on a live diagram and logs press intervals so you can spot dead buttons, missed clicks, and double-click chatter from worn switches.
Is a mouse click test the same as a click latency test?
No. A mouse click test checks whether buttons register at all — one press, one count. A click latency test measures how long each press takes to arrive, in milliseconds. Run the click test first to confirm every button works, then open our mouse latency test if clicks feel delayed rather than missing.
Is a mouse click test the same as a CPS test?
No. A click test checks correctness — every press counted exactly once. A CPS test measures speed — how many clicks per second you can produce in a timed window. Use this page to verify the switches, then the CPS test to benchmark click speed.
Why does one press count twice?
Usually switch bounce: a worn microswitch sends two electrical contacts for one physical press, and the OS reads it as a double-click. If the interval log shows random gaps under ~80 ms on single presses, the switch is chattering — cleaning rarely fixes it permanently, so plan a switch replacement or RMA.
Why do my side buttons do nothing?
Three common causes: a worn side microswitch, the OS or an app remapping back/forward, or a driver profile that disables them. If the counter stays at zero while left and right count fine, check your mouse software bindings first, then treat it as a hardware fault.
How many clicks should I test per button?
Ten slow, deliberate presses per button is a solid sample: every press should add exactly one count. Intermittent faults often survive one press and fail around press five or six, which is why side buttons deserve a second round.
Is this browser click test accurate?
For registration testing, yes — browsers report pointer button events reliably, so a missing or doubled count reflects what your OS actually received. It cannot measure electrical bounce below what the OS delivers, but the ~80 ms chatter heuristic matches the double-click behavior Windows and macOS exhibit with worn switches.
