Mouse tester
Is your mouse working right?
Scroll, click and move. The test finds double clicks, a wheel that jumps back, drift, jumps and a low polling rate. Trackpads too.
Test area: move, click and scroll here
Move, click or scroll in the test area to see it react.
Report a problem
Something odd? Record 10 seconds of what the device does, add a note, and save the file to send us.
- No button pressed.
- Wheel: not moved yet
- Rate: move to measure
- —
How this test works
The run has four steps, a fifth for trackpads: 3 seconds scrolling down and 3 up, 20 clicks with the left button and 20 with the right plus every other button once, 5 seconds with your hand off, then 5 seconds of circles.
The page reads the mouse, wheel and pointer events your browser sends, judges them on your device and keeps nothing.
How to read the result
Each card is one test with its status: pass, warning, fail or not tested. The verdict follows: healthy when every test that ran passed, needs attention when something is off but the device still works, faulty when one failed.
Not tested means too little input, a skipped step, or a browser that can't report what the test needs; the card says which. For the first two, run again with the step's full time. The page shows a trackpad's polling rate and gestures but doesn't judge them.
Common faults
A worn switch bounces, so one press arrives as two less than 80 ms apart: the double click. One on a button is a warning; two on the same button fail.
A dusty or worn wheel sends a step the wrong way; one or two are a warning, three or more over the run fail. A pointer that moves with your hand off, or jumps in the circles, fails those tests; the card says when a weak wireless link dropped samples. A low polling rate is usually a setting, a hub or Bluetooth; the guides say what to try.
What this test can't see
- The sensor's DPI and lift-off distance.
- Your system's pointer acceleration and smoothing: the page sees the pointer after them.
- The switches' debounce time, and buttons your system or the mouse's own software keeps.
- The true polling rate where the browser can't report every sample (it then isn't judged).
- Wireless latency.