Mouse test
Move your mouse over the box, then click inside it.
The readout is live. Movement shows how often your mouse actually reports to the computer; clicks are checked for switch faults as you press.
This is a mouse tester built as a set of measurement tools. Everything runs in your browser, nothing is uploaded, and every verdict quotes the numbers it was based on, so you can check the claim instead of taking it on trust.
The box above is live. Move the pointer across it and the report rate shows how often your mouse is actually delivering movement to the computer. Click inside it and the presses are checked for switch faults as they arrive.
What the live readout means
Report rate is how many times per second your mouse tells the computer where it moved, commonly 125 Hz for office mice and 1000 Hz or more for gaming mice. Most online testers get this wrong in a specific way: they count one movement per drawn frame, which measures your screen's refresh rate instead of the mouse. This page times the underlying input events, which the browser delivers in batches, and it only prints a rate while the capture is steady enough to support one. When the number reads "-", keep the mouse moving continuously for a second.
Events counts every movement report received since the page loaded, and clicks counts presses inside the box. Held buttons are shown while you hold them.
The tools
DPI test. A browser cannot ask a mouse for its DPI; the only honest way to get the number is to measure counts against a known physical distance. This test uses references whose sizes are fixed by standard, a bank card or a sheet of paper, so there is nothing to measure by hand. It reports the spread across passes, and it can solve for your placement error instead of assuming it away.
Double click test. The classic worn-mouse fault is a switch that registers two clicks from one press. The test measures every gap between clicks in milliseconds, flags gaps no finger can produce, and shows your real double-click speed alongside.
Button test. Every button checked for clean presses, releases and held state, including the middle and side buttons. The right button will not open a menu inside the test box, and the side buttons will not navigate.
Keyboard tester. Every key on a live board: press counts, held state, rollover, and re-press timing, with auto-repeat filtered out.
Polling rate test. How often your mouse actually reports, measured from the input events themselves. The reading refuses to print when the capture cannot support it, and the page states exactly which rates have been validated on real hardware.
eDPI calculator. Your DPI multiplied by your in-game sensitivity, which is the speed your aim actually runs at. Useful for keeping your aim identical when you change mouse or DPI step, and honest about only comparing within one game.
Click test. Clicks per second for the left or right button, with the switch's contribution separated out: every gap is screened against the measured 25 ms bounce floor, so a worn switch cannot inflate the score unannounced.
Gamepad tester. A live drawing of your controller that fills as you press: every button, both sticks on a calibration grid, both triggers as bars, and a count of what has registered. It reads Xbox, PlayStation and generic controllers by their standard layout, names every button in words, and states plainly what a browser cannot measure about a controller.
Stick drift test. Where each thumbstick rests with your hands off, measured over three seconds and compared with the dead zones vendors actually publish, so you can see whether the drift you have will show in a game. A second pass checks that both sticks still reach full deflection.
Why a verdict is sometimes refused
A measurement tool that always prints a number is guessing some of the time. When a capture is contaminated, when passes disagree, or when there is simply not enough evidence, these tools say so and decline to print a figure, because a confident wrong number wastes your time in a way an honest refusal does not. Where a claim depends on hardware validation that has not happened yet, the page says that too. The methodology page explains how each measurement works and what has been validated on real hardware.
Frequently asked questions
How do I test my mouse?
Start with the box above: move the pointer to see the report rate, and click to check for switch faults. Then run the specific tool for what you suspect: the double click test if clicks are doubling, the button test if a button feels dead or sticky, and the DPI test if the cursor speed does not match what the box promised.
How do I find out if my mouse is double-clicking on its own?
Click in the box above a few times; a gap under 25 milliseconds between a release and the next press is flagged immediately. The double click test does the same with a full readout of every gap, plus your deliberate double-click speed.
What is my mouse's DPI?
No website can read it out directly; it has to be measured. The DPI test measures it against a bank card or a sheet of paper, both of which have sizes fixed by international standards, so you do not need a ruler.
Why does the report rate show "-" sometimes?
The rate is only printed while the capture is steady enough to support it. Short or hesitant movement does not contain enough evidence, so the readout declines rather than guesses. Move the mouse continuously for about a second and the number appears.
Does this upload anything?
No. Every measurement on this site runs in your browser and nothing about your session leaves your machine. There are no accounts, no uploads, and no server-side processing of any kind.