Mouse Test

A mouse test (also called a Mouse Test or Mouse Tester) checks whether your mouse reports correctly: whether every button is detected, whether one click triggers twice, whether the scroll wheel registers the right direction and how often the mouse reports its position. Choose one of the four tabs above and use your mouse in the test area; the display responds immediately. The test runs entirely in your browser, with no download or sign-up. Nothing is uploaded or saved: the address bar contains only settings (tab and right-click menu), never measurements. It tests your own mouse, not a mouse product. Don't confuse it with the CPS test: the CPS test measures how fast you click, while the mouse test checks whether the hardware reports correctly.

Open the Mouse Buttons tab and click once with each button in the test area: left, right, middle click and, if present, both thumb buttons. Each detected button lights up on the mouse and gets a counter and hold time. If all five buttons are detected, you'll see “5 of 5”. If a thumb button is missing, note that the browser only reports buttons the operating system passes on as mouse button 4 (Back) and 5 (Forward). If the manufacturer's software (for example, Logitech, Razer or Corsair) maps the thumb buttons to a keyboard shortcut, macro or profile switch, the browser won't receive a click. Try setting them to “Back” and “Forward”.

A double-click error makes one click register twice. The usual cause is a worn microswitch whose contacts bounce when pressed. The double-click test measures the time between two clicks of the same button. It flags anything under 50 ms as possible bounce, since a deliberate double-click takes at least about 80 ms. To test, click slowly, about once per second, and make at least 10 clicks. Any flagged click is then a genuine error.

First, use the Double-click test to check whether the mouse really has switch bounce: across 10 slow clicks, no interval should be under 50 ms. If switch bounce is confirmed, depending on the model, your options are a warranty claim, replacing the microswitch (soldering required) or getting a new mouse. For a warranty claim, take a screenshot of the result, since the page address doesn't contain measurements. Some manufacturer programs let you increase the debounce time, but that often only masks the problem temporarily. Also try another USB port and turn off software such as click macros and auto-clickers, which can cause double-clicks without a hardware defect.

Windows treats two clicks as a double-click if the second occurs within 500 ms of the first. That's the default setting. You can change it under Control Panel > Mouse on the “Buttons” tab using the double-click speed slider. Most people's intentional double-clicks are between 100 and 250 ms apart. The test uses the same 500 ms cutoff because the browser can't read your operating system's setting, and shows your shortest interval and the average for your intentional double-clicks.

In the Scroll Wheel tab, turn the mouse wheel over the test area. The test counts each step and its direction, separating up, down and sideways movements. A direction error occurs when a single step in the opposite direction is reported during a steady movement, such as down, down, up, down. Scroll down steadily through at least 20 notches. If the test shows direction errors, dust and lint in the encoder are usually the cause: unplug the mouse, blow compressed air along the side of the wheel while turning it, then test again. For a wireless mouse, a fresh battery or moving the receiver closer sometimes helps. If the test shows no direction errors, the jumping is more likely caused by smooth scrolling in your browser or the scroll speed in the manufacturer's software. If errors persist after cleaning, the encoder is worn out: consider a warranty claim, replacing the encoder or getting a new mouse.

Open the Movement & Hz tab and move your mouse quickly in a circle for at least half a second. The test counts the events reported by the browser, converts them to hertz and identifies the closest standard rate: 125 Hz means 8 ms between reports, 500 Hz means 2 ms, 1000 Hz means 1 ms and 8000 Hz means 0.125 ms. Slower movements produce fewer reports and are ignored so they don't skew the measurement downward. 125 Hz is common for many office mice and is sufficient for work. Gaming mice usually report at 500 or 1000 Hz, meaning every 2 ms or every millisecond. Newer models offer up to 8000 Hz, though the difference from 1000 Hz is small. Set the rate in the manufacturer's software, then use this test to check whether it reaches the browser.

Browsers often send mouse movements to the page only once per frame. The measured rate is then close to your monitor's refresh rate, not the mouse's polling rate. The test therefore shows the source: raw data (pointerrawupdate, Chrome and Edge), coalesced events, or just one event per frame. For the last source, a note indicates that the value is limited. For an accurate measurement, use Chrome or Edge and a mouse connected directly to your computer.

No. DPI is the sensor’s resolution and is only available in the manufacturer’s software. The browser only sees how many pixels the pointer moves, which also depends on your operating system’s pointer speed and acceleration. A website cannot measure sensor quality, lift-off distance, or the delay between a click and the response either. To convert your in-game sensitivity, use the Mouse Sensitivity Converter.

Go through the four tabs in turn to find out which part is affected: if a button is missing in Mouse Buttons, it isn't reporting at all. If the Double-click test shows switch bounce, one click is triggering twice. Direction errors in Scroll Wheel point to the encoder. If the movement trail breaks in Movement & Hz even though you're moving steadily, the connection may be dropping events. Try another USB port or computer; for wireless mice, check the battery and receiver. If your PC doesn't detect the mouse at all, the test can't measure anything either. If everything looks fine in the test, the problem is more likely with drivers, manufacturer software or the mouse surface, since a website can't test the sensor or surface.