Mouse Test
Every button, every wheel tick, and a live movement rate — enough to tell a failing switch from a driver problem.
Buttons, wheel and sensor
Each button has its own counter, and the wheel counts ticks in both directions. A right button that opens a context menu instead of registering is caught by suppressing the menu inside the pad.
Movement rate is estimated from pointer events in the last second. It is not a true polling rate — browsers coalesce events — but a mouse reporting 125 Hz and one reporting 1000 Hz do look different.
Diagnosing a double click
Click once slowly and watch the left counter. If it jumps by two, the switch is bouncing: the usual fix is a new mouse, because the spring inside the switch has lost tension.
A wheel that moves two steps per notch is a worn encoder, and a cursor that stutters across the pad is usually a wireless connection rather than the sensor.
Cleaning up a misbehaving mouse
Dust on the sensor and a tired battery both look like stutter, and both are cheaper to fix than a new mouse. A double click that registers as two is a worn switch and cannot be fixed in software — but it can be confirmed here in ten seconds.
The counters are per session and reset on reload, so nothing accumulates in the background.
How Mouse Test works
Check left, right and middle buttons, count wheel ticks, and see a rough movement rate. Catches a double-clicking switch. The method behind Mouse Test is the single-purpose logic inside wave51.js, and this page shows the result with its assumptions in the open.
- Open Mouse Test and provide mouse test — the page accepts it in the field it shows.
- For Mouse Test, browser APIs and, where stated, one public endpoint do the work.
- The Mouse Test output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.
A worked example for Mouse Test
A typical run of Mouse Test starts with mouse test and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.
Repeat the check on a second network: a result that changes with the network is a routing fact, not a fault in your device. That check applies directly to Mouse Test with mouse test.
When to use Mouse Test — and when not to
Reasonable uses: Diagnosing a connection; Checking DNS or registration data; Testing hardware in the browser. Mouse Test is deliberately narrow: it does one job and states its assumptions instead of hiding them.
Diagnostic apps and terminal tools go deeper but need installs or shell access. For a quick lookup or a device test, a page is the lower-friction path. The honest ceiling for Mouse Test: for Mouse Test, results reflect your network and device.
- Best case for Mouse Test: Diagnosing a connection
- Also fine with Mouse Test: Checking DNS or registration data
- Not what Mouse Test is for: for Mouse Test, results reflect your network and device.
Reading the Mouse Test result
The output of Mouse Test is a function of the inputs alone — no hidden state and no server.
Accuracy and limits of Mouse Test
The method is the single-purpose logic inside wave51.js. Mouse Test prints results at the precision its inputs justify, and the limits below are the honest ones:
- Mouse Test: For Mouse Test, results reflect your network and device.
- For Mouse Test, pages that call an endpoint say so and call it only on your click.
Privacy and speed on the Mouse Test page
The Mouse Test page is a static file plus wave51.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.
Speed follows the build: Mouse Test loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.
What you get from Mouse Test
The output of Mouse Test appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the web work finishes the moment the numbers are in.
Because Mouse Test is built from wave51.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.
Questions
What does Mouse Test do?
Check left, right and middle buttons, count wheel ticks, and see a rough movement rate. Catches a double-clicking switch. Everything runs in your browser; nothing is uploaded.
How accurate is Mouse Test?
The method is the single-purpose logic inside wave51.js. For Mouse Test, results reflect your network and device.
What are the limits of Mouse Test?
For Mouse Test, pages that call an endpoint say so and call it only on your click.
Is anything uploaded when I use Mouse Test?
No. Mouse Test runs entirely in the browser tab; nothing is uploaded, stored or logged.
Can I use Mouse Test offline?
Yes — Mouse Test keeps working offline once the page has loaded; the whole tool is a local script.
Device tests
Keep going
More web tools
Speaker Test
Play a tone on the left, the right or both, check individual frequencies, and run a sweep to hear rattles or a dead cone.
Open toolGamepad Tester
See every button press, both sticks and the axes of a connected controller, with the mapping the browser reports.
Open toolWebcam Test
Open the camera in the page, see the resolution and frame rate it reports, switch between cameras, and stop it cleanly.
Open toolMy Location
Show my exact latitude, longitude and accuracy on one page. The location comes from your browser and stays in your browser.
Open toolScreen Resolution
Your screen resolution, available screen area, browser viewport and device pixel ratio — shown live and updated as you resize.
Open toolDNS Lookup
Look up any domain's A, AAAA, MX, TXT, NS, CNAME or SOA records through a public resolver.
Open tool