Left click
0
Input Testing
Mouse Test
Test every button, scroll wheel, polling rate, and movement. Free mouse diagnostic that runs in your browser.
Desktop with a real mouse is recommended for the full experience.
Test every button, scroll wheel, polling rate, and movement. Free mouse diagnostic that runs in your browser.
Desktop with a real mouse is recommended for the full experience.
0 of 5 buttons tested
0 of 5 buttons testedScroll up and down over the test area.
Scrolled up: 0 px
Scrolled down: 0 px
Scroll smoothness: waiting for wheel input
Waiting for wheel inputMove your mouse quickly across the polling zone.
Move your mouse quickly to capture a polling-rate sample
Some browsers cap polling rate reporting. Exact values may differ from vendor software.
Current: 0 Hz. Peak: 0 Hz. Move your mouse quickly to capture a polling-rate sample.Move your mouse across the canvas to trace a path.
Tracking verdict: waiting for movement
Move your mouse across the canvas to start the tracking test.
Tracking verdict: waiting for movement. Move your mouse across the canvas to start the tracking test.Use a quick screen calibration and a known movement distance to estimate mouse DPI in the browser.
Move your mouse horizontally across this zone after starting the measurement.
Calibration not saved yet
Measured pixels: 0
Estimated DPI: pending
Calibration not saved yet. Estimated DPI: pending.Best used on desktop with a real mouse. Trackpads and touch devices get a reduced experience.
If you do not have a mouse connected, use Keyboard Test or Controller Test instead.
Use the dedicated Scroll Wheel Test if your main issue is skipped scrolling, reverse wheel jumps, or inconsistent mouse wheel behavior. This page stays the broader mouse diagnostic.
Use the mouse button test to confirm left, right, middle, and side-button detection, then scroll inside the contained wheel zone so page scrolling stays unaffected.
Move your mouse quickly inside the polling-rate block to capture a browser-based Hz estimate, then compare the snapped result with common rates like 125, 500, and 1000 Hz.
Trace across the movement canvas to look for jumps or skipping, then use the calibration block if you want a rough estimate of your current mouse DPI.
Start with the button panel because that is the fastest way to confirm whether your left click, right click, middle click, and side buttons register at all. Press each button once, watch the counters change, and use the reset action when you want to restart the session. Then move to the scroll zone and wheel both directions over the contained test area so you can confirm direction, distance, and rough smoothness without breaking page scroll. After that, use the polling-rate block by moving the mouse quickly back and forth for a few seconds. The page will show a live Hz estimate, a peak value, and the nearest common rate such as 125 Hz, 500 Hz, or 1000 Hz. Continue into the movement canvas to draw a trail and look for obvious jumps or skipping, then use the DPI estimation block if you want a rough sensitivity check. The point of this mouse test is not to replace vendor software or a lab tool. It is to give you one honest browser-based mouse tester that checks the basics quickly and helps you narrow down whether the problem is with buttons, the wheel, movement, or raw responsiveness.
A mouse button test sounds simple, but it can reveal several different failure patterns. If the left click or right click does not register at all, the problem may be a worn switch, broken input path, or OS-level issue. If the middle click works only sometimes, the wheel switch can be mechanically inconsistent even when scrolling itself still functions. Side-button testing matters because back and forward buttons often fail before the main buttons on heavily used mice, especially on gaming or productivity models with extra side pressure. The counter view also helps separate dead buttons from unreliable buttons. If a button increments every time, the basic signal path is probably intact. If it misses presses, behaves inconsistently, or only works at certain pressure angles, that is a real clue. The diagram on this page is not meant to imitate every hardware shape exactly. It is meant to make the button test obvious and readable, which is more useful than fancy graphics with weak feedback. That matters for search intent too, because users who look for a mouse button test or mouse click checker usually want an immediate answer, not a tutorial before the input starts working.
Polling rate tells you how often your mouse reports movement data to the system every second. A 125 Hz mouse reports less frequently than a 500 Hz or 1000 Hz mouse, which is why higher polling rates can feel more responsive, especially in fast desktop or gaming scenarios. The browser cannot read hardware polling data as directly as dedicated manufacturer software, but it can still approximate the reporting pattern by counting pointer events in a timed window. That is what this mouse polling rate test does. You move the mouse quickly, the page counts the flow of events, and the result snaps to the nearest common step so the number is easier to interpret. It is still important to stay honest about limitations. Some browsers cap or throttle event reporting for performance and security reasons, so a browser-based polling rate checker should be treated as a practical estimate rather than a lab-grade measurement. Even with that caveat, the section is useful because it quickly tells you whether the behavior looks closer to 125 Hz, 500 Hz, or 1000 Hz instead of leaving you to guess.
DPI is one of the most misunderstood mouse terms because many users treat it as a quality score when it is really a sensitivity measure. Higher DPI means more cursor movement for the same physical mouse distance, but that does not automatically make a mouse better. A very high DPI can feel too twitchy for general browsing, while a lower DPI can feel sluggish for users who expect fast pointer travel. The rough DPI estimation block on this page is not a hardware certification tool. It uses screen calibration and a known movement distance to estimate how many pixels your mouse travels per inch. That is enough to compare general settings, spot obvious mismatch against the value you expect, or sanity-check a device that feels wrong. If the estimate is nowhere near your intended DPI, that can point to driver settings, profile switching, acceleration, or device-level misconfiguration. For exact tuning, vendor software or a dedicated DPI workflow still matters, but for quick troubleshooting a browser-based approximation is often enough.
This mouse tester is useful because it can expose several common problems in one place. Dead buttons are the most obvious case, and the button counters make them visible immediately. Scroll-wheel problems are another major category. If the wheel skips, jumps in large steps, or ignores direction changes, the scroll section can make that pattern obvious. Movement problems show up differently. A smooth trail usually means the sensor path looks stable, while large jumps may hint at surface problems, sensor dirt, wireless instability, or hardware wear. Polling-rate anomalies can point to power-saving behavior, browser throttling, weak wireless performance, or a mouse running at a lower mode than you expected. DPI estimation helps when the pointer speed feels wrong even though buttons and movement seem fine. None of these signals alone is a formal hardware diagnosis, but together they form a practical mouse diagnostic that is much more useful than checking one isolated feature at a time. That is the real reason the page is structured as a hub instead of a tiny button-only widget.
A wired mouse usually gives the cleanest diagnostic path because there are fewer variables between the device and the browser. If a wired mouse misses clicks, scrolls badly, or shows obvious tracking jumps, the issue is more likely to be local hardware, surface quality, or the browser environment itself. Wireless mice add more uncertainty. Battery level, dongle placement, Bluetooth interference, sleep behavior, and receiver congestion can all change how the device feels. That is why a wireless mouse test should be read a little differently. Inconsistent polling rate or occasional movement jumps do not always mean a broken sensor. They can also point to radio conditions or power-saving behavior. This page is still useful for both types because the patterns matter even when the cause differs. The important thing is to read the result in context. If a wired mouse and a wireless mouse behave differently in the same browser on the same surface, that comparison itself becomes valuable diagnostic evidence.
It checks mouse buttons, scroll wheel behavior, polling rate estimates, movement tracking, and a rough DPI estimate in one browser-based diagnostic.
Some mice, browser environments, or OS layers do not expose side-button events consistently. If back and forward buttons do not appear here, the limitation may be outside the page rather than a guaranteed hardware failure.
Polling rate is how often the mouse reports movement data each second. Higher rates can feel more responsive, but browser-based results are still estimates rather than exact hardware readings.
Mouse Test is the broad hub for buttons, scroll, movement, polling rate, and DPI estimation. Double Click Test is the dedicated sibling tool for chatter and accidental double-click behavior.
It can be, but not always. Skipping can come from wheel wear, dirt, switch issues, browser smoothing differences, or OS-level settings. This page helps you confirm the pattern first.
Not with absolute certainty, but it can show consistent symptoms such as dead buttons, unstable movement, and bad wheel behavior that make replacement more likely.
Partly. Basic click and scroll behavior may still register, but side buttons, polling rate interpretation, and DPI measurement are much more meaningful on a real mouse.
Browser throttling, wireless conditions, power-saving profiles, OS settings, or the mouse's current onboard mode can all produce a lower estimate than the marketed number.
It is when movement data arrives unevenly, causing visible jumps or missing motion instead of a smooth path. Sensor issues, wireless interference, or poor surfaces can all contribute.
No. It only listens for normal browser input events and does not write anything to the device or change firmware, drivers, or hardware settings.