How does this mouse tester work?

The page listens to standard browser input events — mousedown, mouseup, wheel, and pointermove — and displays exactly what your operating system reports. If a button lights up here, the hardware, its driver, and the OS are all passing the click through correctly.

Why does my back or forward button not register?

Browsers report side buttons as button codes 3 and 4, but some mice ship with those keys remapped in vendor software, and a few browsers reserve them for page navigation. If they do nothing here, check your mouse utility first — the buttons may be bound to macros or media keys instead of back and forward.

How accurate is the polling rate estimate?

Browsers batch mouse reports and deliver them roughly once per display frame, so a plain event count would cap out near your monitor’s refresh rate. This tool also counts coalesced events where the browser exposes them, which gets much closer to the true rate, but the result is still a lower-bound estimate rather than a lab measurement.

What is a good double-click speed?

Most people double-click with a gap of 100 to 300 milliseconds between presses, and Windows accepts anything under 500 ms by default. If the tester shows very short gaps you never intended — say under 80 ms from a single press — your switch is likely worn and producing accidental double clicks.

Is any of my input sent to a server?

No. Every event is processed by JavaScript running locally in your browser tab, and nothing is recorded, stored, or transmitted. You can disconnect from the internet after the page loads and the tester keeps working.

Mouse Tester

Check every mouse button, the scroll wheel, double-click speed, and an estimated polling rate — all directly on this page.

Buttons

Left

Middle

Right

Back

Forward

Press any mouse button inside this panel. Right-click menu is disabled here only.

Scroll wheel

Scroll here

Up ticks

Down ticks

Last delta

Double-click speed

—

Last gap

—

Best gap

Total clicks

Gaps over 2 seconds start a new measurement. Under 500 ms counts as a double click on most systems.

Polling rate estimate

Move the mouse here during the sample

Browsers batch mouse reports, so this is a lower-bound estimate and may read below your mouse’s true polling rate.

Position and movement

Move the cursor here

0, 0

X, Y in pad

0, 0

Movement ΔX, ΔY

Distance, px

How it works

Press each mouse button inside the button panel — left, middle, right, back, and forward light up the moment they register.
Scroll up and down over the wheel panel to count ticks, then click the double-click target twice to measure the gap in milliseconds.
Start the 2-second polling sample and move the mouse in fast circles over the sample area to estimate the report rate.

Frequently asked questions

How does this mouse tester work?: The page listens to standard browser input events — mousedown, mouseup, wheel, and pointermove — and displays exactly what your operating system reports. If a button lights up here, the hardware, its driver, and the OS are all passing the click through correctly.
Why does my back or forward button not register?: Browsers report side buttons as button codes 3 and 4, but some mice ship with those keys remapped in vendor software, and a few browsers reserve them for page navigation. If they do nothing here, check your mouse utility first — the buttons may be bound to macros or media keys instead of back and forward.
How accurate is the polling rate estimate?: Browsers batch mouse reports and deliver them roughly once per display frame, so a plain event count would cap out near your monitor’s refresh rate. This tool also counts coalesced events where the browser exposes them, which gets much closer to the true rate, but the result is still a lower-bound estimate rather than a lab measurement.
What is a good double-click speed?: Most people double-click with a gap of 100 to 300 milliseconds between presses, and Windows accepts anything under 500 ms by default. If the tester shows very short gaps you never intended — say under 80 ms from a single press — your switch is likely worn and producing accidental double clicks.
Is any of my input sent to a server?: No. Every event is processed by JavaScript running locally in your browser tab, and nothing is recorded, stored, or transmitted. You can disconnect from the internet after the page loads and the tester keeps working.

About this tool

This mouse tester checks the five standard mouse buttons, the scroll wheel, double-click timing, cursor movement, and an estimated polling rate in one page. Each panel responds live: buttons light up while held and keep a press counter, the wheel panel counts up and down ticks with the raw delta value, and the double-click target reports the exact gap in milliseconds between consecutive clicks along with your best time. It is a quick way to confirm a new mouse works before the return window closes, or to diagnose one that has started misbehaving.

Everything runs client-side. The page reads the same DOM events every website receives — mousedown, wheel, pointermove — and simply makes them visible, so nothing is uploaded and nothing about your input leaves the device. The polling-rate panel samples pointer events for two seconds while you move the mouse; because browsers coalesce hardware reports into one event per frame, the tool also counts coalesced events where supported to recover the underlying report rate. Treat the number as a lower bound: a 1000 Hz gaming mouse may read lower depending on browser and display refresh rate.

Typical uses: verifying that a left button with a worn switch is registering phantom double clicks, confirming that side buttons actually send back and forward, checking whether a jumpy scroll wheel skips or reverses ticks, and comparing double-click speed between an old and a new mouse. Right-click is safe to test — the context menu is suppressed inside the button panel only, so the rest of the page behaves normally.

For the most reliable results, test on a hard surface with a proper mousepad, close background software that remaps buttons, and keep the cursor moving continuously during the polling sample. If a button fails here but works in another application, retry in a second browser before blaming the hardware — extensions and OS-level gesture tools can swallow events.