TestMyGearMouse test
Test mouse buttons, double clicks, scrolling and movement in your browser.
Test guide & FAQsMouse test area
MEASUREMENTS
Double-click test
Move the pointer into a test area, then press and release each button, scroll up and down, and drag.
Click normally. A faulty switch may produce extremely short intervals; check the test results.
Double-click test
Same button · down-to-downClick, scroll or move here without rotating the model.
Pointer movement path
Click, scroll or move here to test the mouse path.
This path includes OS and browser processing. No DPI, sensor accuracy or quality score is inferred.
Event register
| Time | Action |
|---|---|
| No input recorded. Move your mouse into a test area to begin. | |
These are inputs received by your browser. Touchpads may also generate pointer and wheel events. Input coverage does not certify hardware health.
Mouse test guide: buttons, double clicks and scrolling
This online mouse tester shows the button, wheel and pointer events received by your browser. Use it to reproduce missing clicks, unexpected double clicks or scrolling problems; an observed input alone does not certify hardware health.
How to test
- Move the pointer into the model or chart area. Press and release the primary, secondary, middle and side buttons one at a time. A button is tested after a complete press and release.
- For the double-click test, select a button and single-click once every one or two seconds. Repeat dozens of times. Review the highlighted short intervals; 100 ms is the default adjustable threshold.
- Scroll up and down in the test area, then drag and trace a path. Check the received direction and events. Save a report and repeat with another USB port or computer if the problem persists.
Frequently asked questions
How do I test mouse buttons and side buttons?
Press and release each button inside a test area and check its received state. Browser navigation or operating-system shortcuts can intercept side buttons. A missing event is a reason to retest in another browser or application, rather than proof of a broken button.
Does the mouse double-click test prove a faulty switch?
No. It highlights short intervals between presses of the same button. Intentional double clicks also produce short intervals. Repeated short intervals during slow, deliberate single clicks are worth investigating; compare another port or computer before drawing a hardware conclusion.
How do I test the mouse scroll wheel?
Place the pointer in a test area and scroll in both directions. Compare the received direction and wheel events with your movement. Trackpads can also send wheel events, so use the mouse you intend to test. Use the page margins or scrollbar to read the guide.
Can this page measure mouse DPI, polling rate or input latency?
It does not measure sensor DPI, USB polling rate or end-to-end input latency. Pointer paths and any browser event-rate readings include operating-system and browser processing. Event delivery can be merged or delayed, so those readings cannot establish the hardware report rate.
How to test & what the numbers mean
Test the input you receive
Move inside the model or chart to capture input. Press and release each button, scroll in both directions and drag with the primary button. The blue highlight means held now; “Observed” means a complete down/up pair was received.
The wheel is captured only inside these areas. Use the page margins or scrollbar to read the rest of the page. Touch and pen input do not count as mouse input.
Read the evidence
To check a switch, select the button and single-click in the test area every one or two seconds, repeating dozens of times. If one click registers as two presses below the configured threshold (100 ms by default), the page flags a possible switch issue. Intentional fast double clicks can also trigger this warning; a short interval does not prove a fault. Retest with another port or device.
This tool does not estimate sensor DPI. JSON includes method, environment, retained data, interruptions and buffer limits; CSV contains the retained raw event register.
Missing input?
Browser navigation and OS shortcuts can intercept side buttons. Swapped primary/secondary settings follow browser button numbers. Ordinary web pages cannot reliably identify a mouse model or distinguish two mice and a touchpad.
Switching windows or hiding the page interrupts an active sample and clears held states without recording a false release. 3D failure does not stop measurements.