Mouse Tests
This hub points to five live mouse tests that run entirely in your browser. The polling rate test shows live Hz and a stability graph. The click test registers all five buttons and flags possible bounce pairs. The scroll test counts wheel steps and direction per event. The drift test counts movement while the mouse is untouched, and the reaction test measures click latency in this browser. No installation, no data leaves your device.
What this measures
- Mouse polling rate: pointer movement samples the browser delivers, with live rate, median, mean, min, max, variation, and a stability graph.
- Click and double-click test: which of the five buttons (left, right, middle, back, forward) the browser receives on press and release, per-button press counts, and pairs of clicks on the same button within 50 ms flagged as possible bounce.
- Scroll test: wheel direction per event, delta value per event, total up and down step counts, and the deltaMode unit the browser reports (pixels, lines, or pages).
- Drift test: movement events the browser reports while the mouse is untouched — event count, pixels accumulated, largest single event.
- Reaction test: click latency from an on-screen signal as this browser observed it, across five trials with a median.
What this cannot measure
- Hardware or firmware polling rate directly — the browser observes only what the OS delivers.
- USB traffic, controller-level timing, or vendor-software readings.
- Switch debounce quality inside the mouse or whether possible bounce is a hardware fault.
- Remapped buttons' original assignment — the browser sees only the remapped output.
- Free-spin versus ratcheted scroll mode or OS-level smooth-scrolling interpolation.
- What causes drift readings — sensor noise, the surface, or software moving the cursor all look the same to the browser.
- True physiological reaction time — the browser number also contains display, browser, and OS pipeline latency.
How to get a steady reading
- Choose the test that matches your suspicion: polling rate for rate stability, click test for switch feel or double-click issues, scroll test for wheel step accuracy.
- For the polling rate test: plug in or charge the mouse, close heavy background apps, move in smooth circles for 30 seconds, keep the cursor inside the test area.
- For the click test: click each button once to confirm registration, then click normally and double-click fast to exercise the switches.
- For the scroll test: scroll slowly for single-step counting, then scroll fast to check for skipped steps, and compare up versus down symmetry.
- When comparing mice, use the same browser, same display refresh rate, and same test duration.
How to read the results
| Metric | What it means |
|---|---|
| Polling rate median | The middle 1-second window value — the number to quote when comparing mice. |
| Variation % | Coefficient of variation across windows. Lower is steadier; above ~10% suggests interference or low battery. |
| Possible bounce pairs | Click pairs on the same button within 50 ms. Shown as count and interval list — not a fault verdict. |
| Scroll steps up / down | Total wheel events counted in each direction this session. |
| deltaMode | The unit the browser reports for wheel deltas: 0 = pixels, 1 = lines, 2 = pages. |
Which test do you need?
Suspect the polling rate is low or unstable? Open the polling rate test. It shows live Hz, a stability graph with drops and spikes shaded, and a variation percentage. The browser-observed number is what the browser delivered — not a hardware measurement.
Feel a double-click when you single-click, or a click that does not register? Open the click and double-click test. It lights up all five buttons on press, counts presses per button, and lists any same-button click pairs under 50 ms as "possible bounce." The browser cannot tell whether that bounce comes from a switch fault, a software double-click setting, or a macro — it only reports what arrived.
Scroll wheel feels like it skips steps or reports the wrong amount? Open the scroll test. It shows each wheel event with its direction, delta, and the deltaMode unit. The same physical wheel movement can report different numbers across browsers and OS settings because deltaMode varies. Compare like with like.
Cursor drifting on its own across the screen? Open the mouse drift test. It measures untouched movement events over 15 seconds to help isolate surface vibration or sensor jitter.
Want to check your input response latency? Open the reaction time test. It measures visual-to-click latency across five trials with browser-pipeline transparency.
How browser mouse testing differs from vendor software
Vendor software (such as G HUB, Razer Synapse, or SteelSeries GG) reads the mouse hardware or USB controller directly. The browser receives input after the operating system processes it. The two measure different things. A 1000 Hz mouse on a 144 Hz display often reads lower in the browser because pointer events align to display frames by default. Even with coalesced events, the browser ceiling caps what can be observed — especially above 1000 Hz.
The click test sees only what reaches the page. If you remap buttons in vendor software or the OS, the test shows the remapped result. If back or forward buttons do not register, the browser or OS may be intercepting them for navigation — that is a delivery finding, not a mouse fault.
The scroll test reports the deltaMode the browser uses. Windows often uses lines (deltaMode 1), macOS often uses pixels (deltaMode 0). The same notch on a ratcheted wheel produces different step counts depending on the unit. The test does not claim one is better — it shows what the browser delivered.
Privacy
All mouse tests run entirely in your browser tab. No mouse movement, click, or scroll data is sent anywhere. No history is stored on any server. You can verify this in DevTools: open the Network tab, run a test, and confirm no requests fire.
Frequently asked questions
What is a mouse tester?
A mouse tester is a browser page that shows what the browser receives from your mouse: polling rate samples, button presses, and wheel events. It runs locally with no installation and no data leaving your device. It does not read firmware or USB packets.
Can a mouse tester replace vendor software?
No. Vendor software reads the hardware directly and can change settings (polling rate, DPI, button mapping). A browser test only observes what the OS delivers to the page. Use vendor software for configuration; use the browser test for a quick, portable check of what the browser actually sees.
Is this the same as a DPI test?
No. DPI (dots per inch) measures how far the cursor moves per physical inch of mouse travel. This site does not offer a DPI accuracy test. The polling rate test measures how often the browser receives position updates per second — a different property.
Does the click test detect double-click faults?
It shows possible bounce: pairs of clicks on the same button within 50 ms, listed with their intervals. It does not declare a fault. A switch bounce, a software double-click speed setting, or a macro can all produce the same pattern. Test on another computer to narrow the cause.
Related tests
Mouse Polling Rate Test
Live Hz, stability graph, and variation — browser-observed, not a hardware measurement.
Mouse Click & Double-Click Test
Five-button registration, press counts, and possible-bounce detection — no fault verdict.
Mouse Scroll Test
Wheel direction, step count per event, totals, and deltaMode unit — compare like with like.
Mouse Drift Test
Counts movement the browser reports while the mouse is untouched — 15 seconds, hand off.
Mouse Reaction Time Test
Click latency from the on-screen signal, five trials, labeled browser-limited.
Last reviewed 2026-10-12