This online mouse test checks that every button on your mouse works and that clicks register the way they should. Left, right and middle buttons each get a live indicator that turns on while the button is held, so you can confirm a clean press and release. It also counts double-clicks and shows scroll-wheel direction, which makes it easy to diagnose the two most common mouse faults: a worn switch that double-fires and a wheel that scrolls the wrong way or skips.
Double-click chatter is one of the most frequent mouse problems. As the micro-switch inside a button wears out, a single physical press can register as two clicks, which breaks drag operations and misfires in games and design tools. To check for it, click slowly and deliberately and watch the click counter: if a single, clearly separate press ever registers as a double-click, the switch is starting to fail. The test also reports the time between clicks so you can see how your own double-click speed compares to the system threshold.
The scroll test tracks each wheel notch and shows the direction and a running delta, which is useful when a wheel feels unreliable. If scrolling up sometimes jumps down, or a notch does nothing, the encoder in the wheel may be dirty or worn. Middle-click, triggered by pressing the wheel itself, gets its own indicator because it is easy to overlook and is a common casualty of heavy use. Right-click is captured too, and the page suppresses the context menu inside the test area so your click is measured rather than opening a menu.
Everything runs locally in your browser using standard pointer and mouse events, so nothing about your clicks is uploaded. That makes this mouse checker a quick, private way to decide whether a flaky mouse needs cleaning, a new switch, or replacing altogether, and to confirm a used mouse works fully before you rely on it.
How this test works
This test listens for mousedown, mouseup, contextmenu and wheel events on a target area and counts them, timing the gap between consecutive clicks with the event timestamps the browser supplies. The double-click detection is our own, based on that gap, rather than the browser's own dblclick event, because a chattering switch produces two clicks a few milliseconds apart and we want to see them as two. What no browser can do is measure your polling rate: pointer events are coalesced and delivered per frame, which the table further down sets out.
How to use the mouse test
- Move your pointer into the test pad so it captures your input.
- Click the left, right and middle buttons and watch each indicator light up.
- Double-click and check that the counter reports a single double-click, not extra clicks.
- Scroll up and down to confirm the wheel direction and step count.
- Look for any button that sticks on, fails to register, or double-fires.
Reference tables
These are server-rendered, so they are readable without running the test and quotable without running any JavaScript. Where a figure comes from a specification it is cited under the table; where it is our own judgement, the table says so.
| What it measures | What it cannot see |
|---|---|
| Left, right and middle button down and up events | Which physical switch is inside the mouse, or its rated click lifespan |
| The time between two clicks, in milliseconds | The exact hardware debounce window; the browser timestamp already includes OS scheduling |
| Scroll direction, wheel delta and cumulative scroll | Physical detent count, because the OS may smooth or accelerate the wheel first |
| Roughly how often pointer events arrive | Your mouse's real polling rate: browsers coalesce pointer events and cap the reported rate |
Compiled by MyGearCheck from the browser APIs each test uses. Every limit listed here is a limit of the browser, not of your hardware.
| Polling rate | Interval between reports | What the browser sees |
|---|---|---|
| 125 Hz | 8 ms | Roughly one pointer event per 8 ms, if nothing coalesces them |
| 500 Hz | 2 ms | Usually fewer events than reports: the browser merges them |
| 1000 Hz | 1 ms | Almost always coalesced; the page sees about one batch per frame |
| 4000 Hz | 0.25 ms | No browser exposes this rate directly |
| 8000 Hz | 0.125 ms | No browser exposes this rate directly |
The interval column is arithmetic: it is one second divided by the rate. The third column is our own observation of how browsers behave, not a specification. Browsers deliberately coalesce pointer events and deliver them per animation frame, so no web page can measure a real polling rate. Any online tool that claims a precise polling-rate reading is reporting how often the browser chose to hand over events, not how often your mouse reported.
Frequently asked questions
How do I test for mouse double-click chatter?
Click slowly and deliberately inside the test pad and watch the counter. If a single clean press ever registers as two clicks, the button switch is likely worn and chattering. Repeating the test a dozen times gives you a reliable picture of how often it misfires.
Why does my scroll wheel scroll the wrong way?
Reversed scrolling is usually a system setting, often called natural or reverse scrolling, rather than a hardware fault. The test shows the raw wheel direction, so if it matches your physical motion here but feels reversed elsewhere, check your operating system scroll settings.
Can I test the middle mouse button?
Yes. Press down on the scroll wheel itself and the middle-button indicator will light up. Middle-click is a common failure point on older mice, so it is worth checking even if the left and right buttons feel fine.
Can this test measure my mouse polling rate?
No, and neither can any other browser page, whatever it claims. Browsers coalesce pointer events and deliver them in batches tied to the display refresh, so what a page counts is how often the browser handed events over, not how often the mouse reported.
Why does the click counter go up when I click the page background?
The test listens on its target area, so clicks outside it are ignored. If a count moves when you did not expect it to, check that the pointer was inside the pad.
Does the test work with a trackball or a vertical mouse?
Yes. Any device the system presents as a mouse produces the same events, so buttons, wheel and movement all register normally.
My mouse skips or stutters. Will this test show that?
Partly. It shows clicks that never arrive and clicks that arrive twice, which covers switch problems. Tracking problems from a dirty sensor or an unsuitable surface show up as jerky pointer movement rather than in the counters.
Why is the time between clicks not exactly what my mouse reports?
Because the timestamp reaches the page through the mouse firmware, the operating system and the browser, each adding a little scheduling time. It is accurate enough to tell a bouncing switch from a human hand, which is what it is for.
Guides for this test
The test shows you what is happening. These explain what to do about it.
More hardware tests
The closest tests to this one are the rest of the input devices group. Working through a whole machine instead? The full check runs everything in order and ends in one report.
Everything else in the suite: