Mouse Tester: Check Every Button, Click, and Scroll

What this mouse tester checks

A mouse looks simple from the outside, but there's more going on than left click, right click, and scroll. This tool checks six separate things, and each one tells you something different about your mouse's condition:

• Buttons and scroll wheel: whether left, right, middle, and any side buttons register correctly, and whether the scroll wheel moves smoothly in both directions.
• Double-click detection: whether a single press is ever being misread as two clicks, the classic sign of a worn switch.
• Drag stability: whether a button stays held down properly through a click-and-drag motion, instead of releasing partway through.
• Cursor tracking: how smoothly your movement is being reported, which points to either sensor quality or surface issues.
• Polling rate: how often your mouse reports its position to your computer, measured in Hz.

Each of these can fail independently. A mouse with a perfectly healthy sensor can still have a dying left-click switch, and a mouse with flawless buttons can still have a scroll encoder full of dust. Testing them separately is the only way to actually isolate what's wrong.

How to use the mouse tester

• Click each button on your mouse, left, right, middle, and any side buttons, and watch for the matching indicator to respond.
• Scroll up and down over the test area to check the wheel in both directions.
• Click and hold, then drag across the screen, to test drag stability.
• Move your mouse in quick circles inside the tracking area to get a polling rate reading.
• Review the live stats panel for anything flagged as irregular, like a double-click warning or an unusually low polling rate.

There's no time limit and no need to rush. Test each function on its own rather than clicking everything at once, it's much easier to isolate a problem that way.

Testing on a laptop trackpad

Trackpads don't have separate physical switches for left, right, and middle click the way a mouse does, so the results look a little different. Left and right click usually work fine since most trackpad drivers map corner-taps or two-finger taps directly to those events. Middle-click and side-button tests generally won't register anything at all, since trackpads don't have a physical equivalent, that's expected and not a fault. Drag and cursor tracking tests still work normally, since those come from the same pointer movement data regardless of whether it's a mouse or a trackpad underneath.

Testing on mobile

If you've connected an external mouse to a phone or tablet via Bluetooth or USB-OTG, this tool will test it the same way it tests a desktop mouse, since the browser is still receiving standard pointer and click events. Tapping the screen directly with your finger is a different kind of input entirely (touch events, not mouse events), so it won't exercise the same button and click logic this tool is built around.

What your results mean

Button and scroll wheel results

This part is the most straightforward: a button either lights up when pressed or it doesn't. If a button doesn't respond at all, work through the troubleshooting steps further down before assuming it's dead. Scroll issues usually show up as skipped steps (scrolling three lines when you expected one), reversed direction, or a wheel that feels like it's scrolling but the test area shows nothing. Skipped or reversed steps almost always point to a dirty or aging scroll encoder rather than anything software-related.

Double-click detection

The tool watches the time between successive clicks on the same button. A single, deliberate press from a human finger almost never produces two full click events within a very short window, so when it happens repeatedly, that's a strong sign the switch's metal contacts are bouncing as they wear out, a problem that gets worse over time and can't be fixed with a driver update or software setting.

Use this rough guide to interpret the interval reading:

Worth knowing: these thresholds aren't a fixed, universal standard. Debounce timing (the small delay a mouse's firmware uses to prevent one physical press from registering as multiple clicks) varies somewhat between manufacturers, and some operating systems let you adjust your own double-click speed setting, which can shift what counts as unusually fast for you specifically. Treat the ranges above as a solid general guide, not an exact spec.

Drag test results

The drag test checks something the basic click test can't: whether a button stays reliably held down through a sustained motion, not just at the initial press. If your click registers fine but items you're dragging keep dropping unexpectedly partway through the motion, that's usually the same worn-switch issue as double-clicking, just showing up differently. Instead of registering an extra click, a failing switch momentarily loses contact mid-press, which your operating system interprets as a release. This is common enough in creative and design work (dragging layers, selections, or objects) that it's worth testing on its own rather than assuming a clean click test means dragging is fine too.

Cursor tracking vs sensor performance

These sound similar but point to different things. Cursor tracking, what you see when you move your mouse inside the tracking area, reflects how smoothly your movement is being reported once it's already passed through your mouse's sensor, its firmware, your USB connection or wireless receiver, and your operating system. If that path shows stutters or sudden jumps, the cause could be anywhere along that chain, not necessarily the sensor itself.

True sensor performance (how well the actual optical or laser sensor reads the surface underneath it) is harder to isolate through a browser test alone, since a browser only ever sees the final, processed movement data, never the raw sensor readings. If your cursor stutters on this test, a few quick things to rule out before assuming sensor failure: try a different surface (glass and highly reflective surfaces confuse a lot of optical sensors), clean the sensor lens, and check whether the same stutter happens in a different USB port or with a fresh battery if wireless.

Polling rate results

Polling rate is how many times per second your mouse reports its position to your computer, measured in Hz. A 500Hz mouse reports roughly every 2 milliseconds, a 1000Hz mouse roughly every 1 millisecond, and so on. Move your mouse in quick circles inside the test area and the tool will show a live and peak Hz reading.

Here's the honest limitation worth knowing: this reading is genuinely reliable for distinguishing common classes like 125Hz, 500Hz, and 1000Hz. But once you get into the 2000Hz-8000Hz range that some newer gaming mice advertise, browser event delivery and your monitor's own refresh rate start to become the bottleneck rather than the mouse itself, since the browser can only process and paint updates as fast as the page and display allow. If your mouse is rated for 4000Hz or 8000Hz and you want to confirm that specific number, your mouse manufacturer's own software will give you a more precise reading than any browser-based tool can, this one included.

Why DPI isn't something a browser tool can truly measure

You might notice this page doesn't include a DPI reading, and that's intentional rather than an oversight. DPI (dots per inch) is a setting built into your mouse's hardware and firmware, and a browser simply has no way to read that value directly. All a browser ever receives is how far your cursor moved in pixels, a number that's already been shaped by your DPI setting, your operating system's pointer speed setting, and in some cases mouse acceleration, all mixed together before it ever reaches the page. Any tool claiming to detect your exact DPI through a browser is estimating backward from that combined number, which is a rough approximation at best, not a real reading of your mouse's hardware setting.

If you want an actual DPI estimate, Rig Vitals' DPI Analyzer is built specifically for that calculation and explains the estimation method and its margin of error in detail. This page focuses on what a browser can check reliably: whether your buttons, scroll wheel, drag stability, and click timing are working correctly.

What this tool can and can't diagnose

Worth being direct about this: everything on this page is read through your browser's input event system, which sits on top of your operating system, which sits on top of your mouse's own USB or wireless connection. That's a few layers removed from the mouse's actual internal hardware. This tool is genuinely good at spotting symptoms, a button not registering, a click firing twice, a scroll step getting skipped, a polling rate that's lower than expected. What it can't do is tell you the exact internal cause with certainty. A button that fails the test could be a worn switch, a loose internal connection, a driver issue, or even a browser quirk, and this tool can't distinguish between those on its own. That's exactly why the troubleshooting steps below exist: they're designed to help you rule causes in or out methodically, rather than assuming the worst from a single failed test.

Troubleshooting common issues

• A button isn't registering at all. Try a different browser first, older browsers sometimes fail to capture side-button events specifically. If that doesn't help, try a different USB port, or for wireless mice, re-pair the connection and check the battery.
• The same button fails on this page but seems to work elsewhere. Some applications remap side buttons through manufacturer software, which can interfere with how the browser sees the raw click. Try closing your mouse's companion software temporarily and testing again.
• Scroll wheel skips or jumps. This is almost always dust or debris inside the wheel mechanism. Compressed air into the wheel housing, combined with scrolling rapidly in both directions a few times, often clears it.
• Double-click warning keeps appearing even with careful, slow clicks. At this point it's very likely a genuine switch fault rather than a testing fluke. It won't fix itself, and it typically gets more frequent over time.
• Polling rate reads lower than your mouse's advertised spec. Check that your mouse's polling rate is actually set correctly in its companion software first, many mice default to a lower rate out of the box. If it's already set correctly, remember that readings above roughly 1000Hz are limited by browser and display behavior, not necessarily your mouse.
• Results seem fine here, but you're still having problems in a specific game or app. That points toward something in that specific software (its own polling handling, input buffering, or settings) rather than the mouse hardware itself, since this test is confirming the hardware and browser layer are working correctly.

FAQ