RigCheckup

Mouse Test

Click, scroll, and move inside the test area below. Every button press is tracked on the mouse diagram.

Last click interval

—

Faults (< 80 ms)

0

Wheel steps

↑0 ↓0

Max polling rate

—

Click any button, spin the wheel, or move fast here to measure polling rate

Collect all your test results on one sheet: PC Checkup Report

What this test checks

If your mouse sometimes registers two clicks when you press once, that's double-click malfunction — worn switch contacts "chatter" and fire twice. Click normally in the test area: intervals shorter than 80 ms between clicks are counted as faults, because a human can't intentionally click that fast. Even one or two faults during normal clicking means the switch is failing.

The polling rate is how often your mouse reports its position to the PC. Move the cursor quickly in circles inside the area: office mice typically poll at 125 Hz, while gaming mice reach 500–8000 Hz. If a high-polling gaming mouse reads far below its rating, check its software settings or try another USB port.

How this test works

Our mouse test listens to the browser's pointer events inside the test area. Pressing a button raises a pointerdown event and releasing it raises a pointerup, and each carries a button number: 0 for left, 1 for the wheel click, 2 for right, 3 for back and 4 for forward. Only events whose pointer type is a mouse are counted. Inside the area the page blocks the context menu, wheel scrolling of the page and the side buttons' back and forward navigation so the test is not interrupted, and the release event is captured on the whole window so that letting go outside the area still clears the button.

Double-click fault detection uses only the timing of left-button presses. Every pointerdown carries a timestamp assigned by the browser; the test subtracts the previous left-press time from the current one, and if the gap is under 80 ms it is counted as a suspected fault. The wheel is read from wheel events, using only the sign of the vertical delta: negative counts as one step up, positive as one step down, and a zero delta is ignored.

Polling rate is estimated from the timestamps of movement events. Browsers coalesce pointer movement into one event per display refresh, so counting events naively only ever shows the monitor's refresh rate, such as 60 or 144 Hz. To get around this the test calls getCoalescedEvents, which returns the original samples the mouse reported before they were merged. It keeps the samples from the last second, and once at least 20 are available it divides the number of intervals by the span of time they cover to produce a Hz figure, recording the highest value seen during the session. In a browser without coalesced-event support the reading converges on the display refresh rate instead.

Click timings, movement samples and wheel counts are computed in the browser's memory and never transmitted anywhere. Pressing Reset or closing the page discards them.

How to read the results

The mouse diagram shows five buttons: left, right, wheel click, back and forward. A button lights up while it is held and keeps a tested marker once it has been pressed. If you press a button and nothing happens, its signal is not reaching the browser. Side buttons are the usual exception, because vendor software often reassigns them to macros or DPI switching, in which case the browser never receives a button event, so check those settings first.

Last click interval is the time in milliseconds between the previous left press and the latest one. Ordinary single clicks at a normal pace produce several hundred milliseconds or more, and even a deliberate double-click usually exceeds 100 ms. Faults counts how many intervals fell below 80 ms. That threshold was chosen because roughly 80 ms is about the fastest a finger can intentionally repeat a click, while a spurious second click caused by bouncing contacts arrives within a few milliseconds to a few tens of milliseconds. So if the counter rises after a single press, switch chatter is almost certainly the cause; if it rises only while you are spam-clicking as fast as you can, a healthy mouse can produce that too.

Wheel steps shows separate counts for up and down. Turning the wheel slowly one notch at a time in a single direction should advance only one counter, one step per notch. Several counts per notch is normal on free-spinning or smooth-scroll wheels, but counts in the opposite direction mixed in, or counts that change when the wheel is not moving, point to a worn or dirty encoder.

Max polling rate is the highest Hz measured in the session. 125 Hz is the default for office mice and many wireless models, 500 and 1000 Hz are the usual gaming settings, and higher figures come from mice running a high-speed mode. Slow movement gives the sensor little to report, so the figure under-reads unless you move fast; draw large, quick circles inside the area for a few seconds to reach the maximum. A reading stuck near half the configured rate, for example 500 Hz from a 1000 Hz mouse, can come from browser batching or USB bandwidth limits, while a reading pinned at 125 Hz usually means the rate was never changed in the vendor software or the mouse is in a wireless power-saving mode.

When to use it: common situations

Suspected double-clicking before the warranty runs out. If drags occasionally drop or files open on a single click, come here and left-click about a hundred times at your normal pace. If the fault counter rises even once, the switch is nearing the end of its life. While the warranty is valid, a replacement based on this result is the cheapest fix available.

Checking a used mouse at purchase. As soon as it arrives, press every button and confirm each one shows on the diagram, left-click a hundred times and look for faults, then scroll the wheel both ways and make sure no opposite-direction counts creep in. Those three checks catch most of the common defects in a second-hand mouse.

Confirming that a polling-rate change was applied. After switching from 500 to 1000 Hz in the vendor software, move the mouse fast before and after the change and compare the maximum readings. If the number does not move, the setting was not saved or a different profile is active.

Diagnosing wireless lag. When the cursor occasionally freezes or jumps, watch whether the polling rate stays steady during continuous movement. Large swings in the reading suggest 2.4 GHz interference or a battery-saving mode. Moving the receiver closer to the mouse on a USB extension, or testing the same mouse over its cable, narrows the cause quickly.

Scroll wheel misbehaviour and side buttons after a driver reinstall. A wheel that occasionally scrolls backwards shows up immediately as mixed up and down counts. After reinstalling drivers or vendor software, pressing both side buttons and checking that they appear on the diagram tells you whether the button assignments have returned to their defaults.

Limits of a browser test and what to check elsewhere

A browser only sees what the operating system passes on. Because events are grouped per display refresh, even with coalesced events restored an ultra-high polling rate of 4000 or 8000 Hz can read lower than the true value. The test also cannot measure click latency below the millisecond level or sensor behaviour such as acceleration, tracking jitter and lift-off distance, and it does not measure switch wear directly; it only reveals chatter, which is the consequence of wear.

Operating system settings play a part. Enhance pointer precision on Windows, the mouse acceleration setting, does not change the polling rate but does change how movement feels. The OS double-click speed setting determines what the system treats as a double-click and is independent of this test's 80 ms rule. Button remaps, macros and debounce settings in vendor software alter the signal before the browser receives it, so returning them to defaults before testing gives the most honest picture.

When something looks wrong, isolate the cause next. Try the mouse on another PC or in a USB port on the machine itself rather than a hub, and if it is wireless, test it over the cable as well. If the vendor software offers a debounce time, try increasing it, and apply any firmware update. For how the mouse feels in a game, the in-game polling or input-latency display, or a dedicated measurement tool, will be more precise than a browser.

For more detail, our double-click malfunction guide walks through every fix from switch replacement and contact restoration to software workarounds. The polling rate guide explains the difference between 125 and 8000 Hz and how to change the setting. The scroll wheel guide covers encoder cleaning and replacement, and the cursor stutter guide works through wireless interference, drivers and USB power management in diagnostic order.

Frequently asked questions

The suspected fault counter went up. Is my mouse broken?
If it went up after a single deliberate click, probably yes. An intentional double-click usually has a gap of 100 ms or more, so two clicks less than 80 ms apart almost always come from worn switch contacts bouncing. Rapid intentional spam-clicking can also trigger it on a healthy mouse, so test with slow, normal single clicks.
My polling rate reads lower than the spec.
You need to move the mouse fast, in large circles, to reach the maximum — slow movement produces less data and a lower reading. Browsers also batch pointer events to the display refresh rate, so ultra-high-rate mice of 4000 Hz and above can read lower than they really are. If a 1000 Hz mouse stays near 125 Hz, check the rate setting in the vendor software and try a different USB port.
Pressing the side buttons navigates away from the page.
With the cursor inside the test area, the page blocks navigation and only records the button press. Outside that area, the browser's normal back and forward actions apply, so check where the cursor is. If you have assigned the side buttons to something else in the vendor software — a macro or a DPI switch, for example — the browser may never receive the button signal at all.
One wheel notch adds several counts, or counts in the opposite direction.
Smooth-scrolling mice and trackpads split one gesture into many events, so several counts per movement can be normal. But if you scroll slowly in one direction and counts for the opposite direction are mixed in, that is the classic sign of a worn or dusty wheel encoder. Blowing compressed air into the gap around the wheel is the first thing to try.
Does it work with a trackpad or touchscreen?
Clicks and scrolling are recorded from a trackpad. However, double-click fault detection and polling rate measurement are designed for mice with physical switches and sensors, so they do not produce meaningful values on a trackpad. Touchscreens have no concept of mouse buttons and are outside the scope of this test.

Related guides