CLICK · SCROLL · MOVE · CHECK
Mouse Tester
Test mouse buttons, scroll wheel, held clicks, rapid repeat behavior, and browser-observed pointer rate directly in your browser.
No account. No upload. Your clicks and movement stay in this page. Browser measurements can reveal input behavior, but they cannot certify hardware condition.
Move the pointer here. Click each mouse button, hold a button, and scroll in both directions. Right-click and wheel behavior are captured inside this test area.
Move, click, hold, and scroll inside the diagnostic area.
10-click rapid-repeat check
Start the check, then deliberately single-click the primary button ten times at a comfortable pace. The app reports unusually short intervals as observations, not proof of a failing switch.
What this mouse tester can actually tell you
A browser can observe many mouse-compatible input events directly: button presses and releases, wheel activity, pointer movement, event timing, and some side-button input. This app turns those events into a readable local diagnostic instead of claiming access to hardware data the browser does not expose.
Test mouse buttons
Primary, secondary, middle, Back, and Forward are tracked separately. The labels follow browser button roles because a left-handed or remapped mouse may not match the physical left/right layout.
Test the scroll wheel
Scroll up, down, and horizontal wheel activity are recorded when the browser exposes them. Wheel events can use pixel, line, or page units, so this app focuses on direction and event behavior instead of pretending every delta has the same physical meaning.
Check rapid repeat behavior
The 10-click screen records the time between deliberate primary-button presses. Intervals under 80 ms are flagged as rapid observations. That threshold is a screening aid, not an industry hardware-failure standard.
Browser-observed pointer rate is not a USB polling-rate measurement
The movement panel estimates how frequently pointer updates become available to this page during active motion. Browsers may coalesce underlying device updates, operating systems may schedule events differently, and high-resolution pointer APIs are not identical across browsers.
Interpretation boundary: a result such as ~950 Hz means this page observed movement updates at roughly that cadence during the sampled motion. It does not prove that the mouse USB report rate is exactly 950 Hz.
How to test a mouse methodically
- Move the pointer around the diagnostic area for several seconds.
- Press and release every button your mouse provides.
- Hold the primary button briefly to confirm press-and-hold behavior.
- Scroll up and down; test horizontal scrolling if the hardware supports it.
- Run the 10-click repeat check at a normal deliberate pace.
- Reset and repeat unusual results before treating them as meaningful.
What this test cannot diagnose
Mouse Tester cannot read firmware health, electrical switch wear, battery condition, driver state, USB packet captures, true end-to-end input latency, sensor DPI, or radio interference directly. Some browsers or operating systems may reserve side buttons before a page can use them. Trackpads may also appear as mouse-compatible input.
If something looks wrong
Repeat the test first. Then try another browser and, if practical, another USB port or computer. Check vendor/remapping software and wireless battery state. A repeated abnormal result across environments is more informative than one unusual browser session.
Why does right-click not open the normal context menu in the test area?
The test area suppresses its normal context menu so the secondary button can be observed without the browser menu covering the diagnostic surface. Right-click works normally outside the test area.
Why did a side button not register?
Some browsers, operating systems, extensions, and mouse utilities reserve Back or Forward actions before the page receives a usable event. Try another browser and check remapping software before assuming the physical button has failed.
Can this measure mouse DPI?
No. Browser pointer coordinates are affected by operating-system pointer settings, browser scaling, acceleration, and screen geometry. A separate calibrated DPI workflow would need a different product contract.
Can this measure input lag?
Not end-to-end hardware latency. This page can measure intervals between browser events, but that is not the same as the delay from physical switch actuation through hardware, USB, operating system, browser scheduling, and display response.
Does a rapid pair prove my mouse is double-clicking?
No. It is a timing observation from one run. Repeat the check and compare another browser or computer before drawing a hardware conclusion.
Are my clicks or movement saved?
No. Diagnostic state stays in the current page memory and is discarded when the page is refreshed or closed. Copying a summary happens only when you choose Copy summary.