Mouse test · no permissions needed
Mouse Test: Buttons, Double Click, Scroll Wheel & CPS
See what your browser receives from your mouse. Check every button, inspect click intervals, observe vertical and horizontal wheel events, then measure your CPS.
Check each mouse button
Press buttons inside the test area. Pressed, tested and untouched states stay separate so you can inspect one control at a time.
Back and Forward buttons can be reserved by your browser or operating system. A missing event does not prove a hardware fault.
Recent browser events
No events yet
Reading the results
What the numbers can tell you
Every value above is a browser event, shown exactly as received. Read these three before drawing any conclusion about your mouse.
Interval chips and the dblclick counter
Each chip is the time between two consecutive clicks of the same button, newest first. The dblclick counter only goes up when the browser itself joins two clicks into a double click, based on your operating system’s double-click speed. If you pressed once but a new chip shows a very short interval, or the dblclick counter goes up, that press reached the browser as two clicks. Repeat it several times, then compare another browser and another computer before blaming the mouse.
“Not detected” on Back or Forward
Not detected means this page has received no event from that button since it loaded or was last reset. Browsers and operating systems often reserve Back and Forward for page navigation, and mouse software can remap them, so the press may never reach the page. Treat it as a missing event, not as a fault. A button the browser reports with a code other than 0 to 4 is listed under Other button codes instead.
Two buttons at once in Chrome
When you hold one button and press a second, or let go of one of two held buttons, Chrome reports the change as a pointer move with a new Buttons bitmask, not as a separate press or release. The button tiles follow that bitmask, so both buttons still light up. The recent events list only records presses, releases and clicks, so it may skip the second press or show a release with no matching press. The bitmask adds 1 for left, 2 for right, 4 for middle, 8 for Back and 16 for Forward.
Privacy by design
Your raw test data stays in this browser
Mouse buttons, coordinates, event timing, wheel deltas and event history are not sent to our analytics service.
Browser storage
Only CPS best scores, grouped by test duration, are saved in localStorage. You can clear them at any time. Raw event history is kept in memory and disappears when you leave or reload.
Usage analytics
If analytics is enabled, our custom event payload contains only fixed summaries: language, mode start, mode completion, reset and local-record clearing. Automatic page views, Google Signals and ad personalisation are disabled. Google Analytics may still process standard connection and browser metadata, but it never receives a button code, interval, wheel delta or score from this tool.
Permissions and uploads
The tests use standard browser pointer, wheel, keyboard and audio output APIs. They ask for no camera, microphone or device permission: the sound test only plays audio and never records. No test data is uploaded.
Mouse test questions
Can this test prove my mouse is broken?
No. It shows only the events delivered to this browser. Drivers, browser settings, extensions and the operating system can affect what appears.
Why do Back or Forward buttons show nothing?
Some browsers and operating systems reserve side-button actions. Compare browsers and computers before drawing a hardware conclusion.
Are wheel delta values the physical wheel steps?
No. Their units depend on deltaMode and browser processing. They must not be interpreted as DPI, polling rate or hardware latency.
Does a keyboard press or screen tap count toward CPS?
No. The CPS area counts physical left-button pointer input and ignores touch, pen and keyboard activation.