Mouse Tester

Diagnostics
Seconds
ms
Next

Use this mouse tester to check common pointer hardware directly in the browser. The tool records primary, middle, secondary, back and forward button events, tracks wheel deltas, draws a live movement trail and estimates double-click timing. It is useful after changing a mouse, troubleshooting a gaming mouse, checking a laptop trackpad or confirming that browser side buttons are being detected.

How to test a mouse

  1. 1

    Set the timing window

    Choose how many seconds of pointer movement should be included in the movement sample and set the double-click window you want to compare against.

  2. 2

    Use the test pad

    Move the pointer across the pad, press each mouse button and scroll the wheel. The diagnostics update immediately in your browser.

  3. 3

    Read the summary

    Compare button counts, wheel totals, pointer sample rate and the estimated double-click interval to identify missed clicks or unusual input behavior.

What the browser can report

Mouse and pointer diagnostics in a web page come from standard browser events. A press on the test pad is read from MouseEvent.button, wheel motion is read from WheelEvent.deltaX and deltaY, and movement is sampled from pointermove timestamps. The values are useful for checking whether the browser receives the input, but they are not a laboratory measurement of hardware latency.

Input Browser value What to check
Primary button button = 0 Left click or main click fires once per press
Middle button button = 1 Wheel click is detected separately from scroll
Secondary button button = 2 Right click appears without opening the context menu
Back button button = 3 Side back button reaches the page
Forward button button = 4 Side forward button reaches the page
Wheel deltaX, deltaY Vertical and horizontal scroll deltas change

A practical check

Suppose a mouse skips double-clicks in a game. Set the double-click window to 500 ms, then click the primary button twice at the pace you normally use. If the interval appears around 180 to 350 ms, the browser is seeing a normal double-click pattern. If only one primary press appears, or the interval is far outside your usual timing, repeat the test on another USB port or another browser to separate hardware issues from browser behavior.

Pointer movement sampling

The movement sample is a simple rolling count of pointermove events over the selected time window. A higher number means the page is receiving more movement events per second. This depends on the browser, operating system, mouse polling rate, display refresh rate and whether the pointer is moving. It should be treated as a quick diagnostic signal, not a guaranteed polling-rate certificate.

Common pitfalls

  • Browser back and forward buttons can be intercepted by the browser or operating system before a page sees them.
  • Trackpads may emulate mouse buttons and wheel deltas differently from a physical mouse.
  • High wheel totals do not always mean faster scrolling because browsers normalize devices in different ways.
  • A wireless mouse with a low battery can pass a basic click test but still show intermittent movement or scroll behavior.

Frequently Asked Questions

No. Button presses, wheel movement and pointer samples are processed locally in your browser. The diagnostic values are not uploaded by the tool.

Some browsers, drivers and operating-system settings reserve side buttons for navigation before the page can read them. If the buttons do not appear here, test another browser and check the mouse driver mapping.

No. The movement sample counts pointermove events received by the page over a short window. It is helpful for spotting input activity, but dedicated hardware tools are better for exact polling-rate certification.

Many users double-click between about 200 and 500 ms. Operating systems often let you adjust the accepted interval, so use this estimate as a quick comparison rather than a universal pass or fail rule.

Related Tools