Mouse Test

Use polling, jitter, DPI, and scroll diagnostics only when those measurements answer the problem you are checking.

Move, click, double-click, drag, and scroll here

—Last button

—Pointer position

0Clicks

0Wheel events

—Pointer type

—Recent event Hz

0Buttons bitmask

0Double-clicks

ReadyMovement 0, 0 · buttons bitmask 0

Mouse diagnostics

Polling rateInspect browser-visible event cadence and stability.Movement traceInspect path smoothness and direction changes.Effective DPIRelate pointer pixels to measured physical travel.Wheel eventsInspect delta direction, mode, cadence, and reversals.

This page verifies events delivered to the browser. It cannot certify switch debounce, sensor hardware, USB firmware, or end-to-end click latency.

What the browser can measure

Start with a functional check, measure only what the browser can actually expose, then retest after one change.

ConnectChoose the actual browser-visible device or grant permission when required.

TestConfirm basic signal, input, output, preview or display behavior.

MeasureUse browser-exposed levels, timing, resolution, FPS, axes or event data.

DiagnoseCompare the symptom with the specific diagnostic instead of relying on one number.

RetestRepeat after changing the device, cable, permission, browser or system setting.

Pre-call Mic Webcam Keyboard Gamepad Display Permissions

Browser boundary
These tools observe browser APIs and local media/event streams. They cannot certify hardware condition, bypass denied permissions, or expose measurements the browser/OS does not provide.

Mouse Test: Polling Rate, Buttons & Interaction Audit

Turn live mouse diagnostics into a polling-rate and interaction audit covering buttons, clicks, double-clicks, wheel activity and movement evidence.

Target polling rate (Hz)

Button, wheel, click-gap and browser cadence evidence

Keep using the original mouse test zone above; this panel organizes the same browser events into per-control evidence for troubleshooting.

Press each button, scroll both directions, then move steadily inside the original test zone.

What this tool checks

Verify browser-visible mouse buttons, movement, coordinates, wheel behavior, dragging, double clicks and recent pointer cadence.

How to use the result

Use polling, jitter, DPI, and scroll diagnostics only when those measurements answer the problem you are checking.

Privacy & browser limits

Device streams and input events used by this page are handled in your browser unless the page explicitly says otherwise. Permission, label, timing and hardware-field availability depend on the browser and operating system.

Browser pointer delivery is kept distinct from USB polling

Button, movement, wheel and pointer-type events confirm what reaches the page. Event cadence is not presented as a hardware USB polling-rate certification.

Practical guide and verification

Use the tool first, then use these checks to interpret, verify and hand off the result without displacing the primary workflow.

Test each physical control separately

Press left, middle, right, back, and forward one at a time inside the test zone, then scroll in each direction. A per-button count helps distinguish a control that never reaches the browser from a control that registers inconsistently. Retest in another browser before concluding that hardware is faulty because extensions and browser shortcuts can intercept events.

Interpret double-click timing as event evidence

A short click interval can be intentional or can reflect switch bounce. Repeat slow single-click trials and normal double-click trials rather than diagnosing a device from one pair. The browser exposes event timing, not the electrical switch waveform, so use the pattern as a troubleshooting clue rather than a hardware certification.

Treat polling rate as a browser-visible estimate

Pointer events may be coalesced, throttled, or affected by display refresh, operating-system settings, browser scheduling, wireless conditions, and background load. Compare median event cadence with a reference value, but do not present the reading as proof of the USB report rate printed on a device specification.

Change one variable and retest

If movement, clicking, or scrolling looks inconsistent, repeat the same test after changing only one factor—browser, port, surface, wireless mode, or system setting. Keeping the procedure consistent makes before/after evidence more useful than changing several conditions at once.