We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Free online mouse tester to check your left, right, and middle buttons, plus scroll wheel. Quickly detect hardware issues and broken clicks.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This online mouse tester records browser-visible mouse button and wheel events while the page is open. Click to check left, middle, right, back, and forward buttons; scroll in both directions to see wheel counts. The display includes totals, the most recent event and pointer position when available. A registered click means the browser received that input during this run.
The page also counts two left clicks within 500 milliseconds as a double-click sample and includes a timed clicks-per-second test. The CPS result is the observed click count divided by elapsed test time. It describes the events registered during that test, not a certified measurement of switch response or device performance. Testing one button and one wheel direction at a time makes the counters easier to interpret.
A browser event check is useful for confirming whether input reaches a webpage. It cannot inspect the mouse sensor, measure DPI or polling rate, identify a worn switch electrically, or determine whether a driver or operating system remapped an input.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Keep the page active, then click each button you want to check. The counts and status show inputs the browser reports; a button your mouse does not have will naturally remain unused.
Scroll upward and downward and compare the separate direction counters. Use several deliberate movements if the wheel sometimes skips.
Use ordinary left clicks to populate the double-click sample. Two clicks within 500 ms increment the double-click count; this threshold is a quick screen and not a universal definition of a faulty switch.
Select one of the offered durations (1, 5, 10, 30, or 60 seconds), start the test, and click during the interval. The result is average clicks per second for that run.
Reset the counters before testing another mouse or changing settings so each set of event counts starts cleanly.
Repeat the same button presses and wheel motion under the same browser and device conditions. If a side button does not register, check whether the operating system or mouse software assigns it a browser navigation action. If the result changes between applications, that difference can help narrow down where the input is handled.
Use cases
See how the tool fits into real work and everyday tasks.
Confirm that the primary buttons and scroll directions generate events before installing a device-specific utility or changing assignments.
Repeat a short sequence and compare individual button counts. A missed or repeated event is a reason to investigate the connection, settings, or device further.
Check back and forward buttons in the browser and note whether they are reported as mouse input or trigger navigation under the current setup.
Q&A
Find concise answers to common questions and confusing cases.
It confirms that a matching mouse event reached the page during this run. It does not prove the physical switch or sensor is healthy in every application.
Two left-button events no more than 500 milliseconds apart add one to the sample count. Repeat deliberate clicks to see whether extra events appear unexpectedly.
No. It checks page-level button and wheel events and provides a timed CPS sample. It does not measure DPI, polling rate, sensor accuracy, or hardware condition.
Some browsers or system settings may handle side buttons differently, or the mouse may not have those buttons. Check the button assignment and try another browser or computer if appropriate.
Notes
Review scope, result limitations, and important precautions before use.
Counts reflect input events delivered to the page. Browser behavior, operating-system shortcuts, remote desktop software, accessibility settings, extensions, or device remapping can change which events arrive. A missing count alone does not diagnose a broken mouse, and a count does not certify the sensor or switch.
The double-click interval and CPS result are simple observations from the current run. They are not standardized hardware benchmarks; compare repeated results under similar conditions and use device diagnostics or manufacturer support when you need to assess physical hardware.
Related
Discover related tools, collections, and available API capabilities.