Use this online mouse test to light up every button, compare pressed and released states, measure click gaps, hold and drag, inspect a wheel timeline, and estimate browser-observed event frequency.
Ready for input
Choose a mode in the controls. The live input area stays beside it on desktop, while mobile actions take you directly to the same test area.
Start the sample, then make five deliberate left clicks about one second apart. Exact gaps are measured so a very short repeat is visible.
Start a clean sample before clicking in the panel.
Arm the test, then hold the left button and keep the mouse moving inside the panel for 1.5 seconds.
Ready to arm.
Run the dedicated three-attempt mouse drag test →Start the two-second sample, then move continuously in fast circles. Coalesced pointer samples are used when the browser exposes them.
Start a clean two-second sample, then move continuously in the live area.
Scroll steadily in one direction for several steps, pause, then reverse. Vertical and horizontal events are separated, and a lone opposite input is marked as a possible reversal.
Start a clean wheel trace before scrolling in the live area.
Complete the three core checks while the matching mouse part and counters update live.
This mouse tester shows whether the expected event reached this tab. A focused diagnostic can expose a repeatable timing or release pattern. Neither one certifies the electrical condition of a switch, wheel encoder, cable, receiver, firmware, or sensor.
Movement, required buttons, or both wheel directions reached the browser.
Hold, double-click, wheel, and polling results describe this sample—not every future input.
Repeat the same action in another browser, port, connection mode, or computer.
Change one condition at a time. That turns a vague symptom into a useful comparison.
Reset the checker, keep this tab active, and repeat the incomplete step at a steady pace.
Compare another browser, application, USB port, wireless mode, or computer—not several changes at once.
A warning is a browser-observed pattern. Repeatable warnings are useful evidence, but they do not identify the physical component by themselves.
This tool interprets standard browser mouse, wheel, and pointer events. The polling sample reads coalesced events when exposed; the specification leaves browser coalescing behavior implementation-dependent. See the W3C definitions for mouse button values and wheel direction data.
Use the mouse button test area, press each button, and scroll in the directions your device supports. The diagram lights up while a standard button is held, while counters separate press and release events. Focused tests can then measure click gaps, a held drag, polling frequency, and recent wheel direction.
No. A browser test can expose missing events or repeatable timing and release patterns, but it cannot inspect a switch, wheel encoder, firmware, USB connection, receiver, or sensor. Repeat the same focused test under one changed condition before diagnosing hardware.
No. Pressing the wheel sends a middle-button event, while rolling it sends wheel-direction data. This checker shows the middle-button press separately and animates the wheel for vertical or horizontal scrolling.
Keep the pointer over the test panel and scroll several steady steps in one direction before reversing. Vertical and horizontal counters confirm browser-visible delivery, while the recent-event timeline highlights an isolated opposite-direction event between matching inputs. Repeat any warning at the same pace.
Start the five-click sample, then make five deliberate left clicks about one second apart. A browser-recognized double-click or very rapid re-press is shown as a potential warning. Repeat the sample slowly because intentional fast clicking can produce the same event pattern.
Arm the hold test, then keep the left button pressed while moving for 1.5 seconds. An early release event interrupts the test. Repeat an interruption before treating it as evidence, because releasing the button early by hand produces the same result.
The two-second test estimates the event frequency observed by this browser and uses coalesced pointer samples when available. Browser scheduling, operating-system processing, and event coalescing can lower the reading, so treat it as a comparison value rather than a certified USB polling rate.
No. Polling rate describes observed event frequency, while DPI requires comparing movement counts with a measured physical distance. Use the separate mouse DPI checker for that estimate.
No. Event counters and the current result remain in this browser tab. The page does not require an account or upload a pointer path.