How do I test mouse buttons, holds and scrolling?

Press each button inside the stage and watch its count and light. A held button stays lit until the page receives a release, cancellation or loss of focus. Scroll up, down or sideways to inspect wheel direction and travel. Move in the drawing area to leave a trail, or hold a button while moving to observe the hold and movement together. This is an input-event check, not a drag-and-drop target.

Why does right-clicking not open the context menu here?

The page prevents the context menu inside the stage so you can count right-button presses there. It also asks the browser to prevent wheel autoscroll, side-button navigation and page scrolling inside that stage. Outside the stage these actions behave normally; some browser or driver actions may still take precedence.

What is polling rate, and why does mine read 60 Hz?

Hardware polling rate is how often the mouse reports to the computer. This page instead estimates the rate of movement samples delivered by the browser, including getCoalescedEvents samples when available. Event merging, timestamp precision, motion, system load and browser scheduling affect the result. It compares the estimate with animation-frame delivery measured over at least half a second, not with a verified display specification. A value near 60 Hz can be consistent with frame-limited event delivery, but neither a low value nor a value above the frame rate proves the hardware rate or its cause.

What do the double-click and rapid-pair results mean?

This tool pairs non-overlapping left clicks that arrive within 500 milliseconds and 10 CSS pixels. It uses those fixed limits rather than reading your operating system settings or counting native dblclick events. A pair below 50 milliseconds is labelled a rapid pair. Press once deliberately, wait, and watch for unexpected extra presses; the event count can document what arrived, but timing alone cannot tell whether a switch, input software or an intentional clicking technique caused it.

Why do my back and forward buttons not show up?

The browser names side-button events as Back and Forward, button numbers 3 and 4. A driver may map a thumb button to a keyboard shortcut or another action instead, and browser navigation can take precedence. Extra button numbers are counted separately. A missing event does not establish that a physical button is absent or broken.

Does the wheel count work with a trackpad or Magic Mouse?

Yes, when the browser delivers wheel events. The counts are events in each direction, not physical wheel notches or individual gestures: drivers, smooth scrolling and trackpad momentum can produce several events for one action. Travel sums the reported deltas in CSS pixels, using 16 pixels for a line-mode unit and the window height for a page-mode unit. Pinch gestures delivered as Ctrl plus wheel are left to browser zoom and are not counted.

What does the mouse speed test measure?

Pointer speed is the recent path length divided by the time between captured movement samples inside the drawing area, in CSS pixels per second. The path retains up to 4,000 samples, breaks when you leave the area, and excludes intervals of 50 milliseconds or longer. System pointer speed, acceleration, browser zoom and sample delivery affect it. It is a screen-pointer measurement, not physical hand speed, mouse DPI or a click-speed score.

Can this test mouse DPI, sensor accuracy or hardware latency?

No. A page receives pointer coordinates after the device, driver and browser have processed them. DPI needs verified sensor counts and physical distance; hardware latency needs a physical timing reference. The trail can show the pointer path you observed, including visible jumps or drift, but cannot isolate a sensor fault, acceleration or delay. The tool does not calibrate the mouse or change sensitivity settings.

Can I test a gaming, wireless, Logitech, Razer or vertical mouse on a Mac or laptop?

A connected mouse can be checked here when its browser reports the button, wheel and movement events. The same applies to a laptop touchpad and a mouse connected to an Android device. A finger or pen is ignored. Model-specific buttons, battery level, wireless signal strength and device software features are not exposed by this test.

Does anything leave my computer?

The event records used by the test stay in this browser tab. They are not uploaded or saved between visits. Reset clears the recorded counts and trail, and reloading starts again.

Mouse Test

Click, scroll and move inside the stage to see the events your browser receives. Button counts, held-button lights, wheel direction, click-pair timing, a pointer trail and CSS pointer speed appear together. Reset starts a fresh test.

move to draw · click to mark · scroll to fill the meter

Waiting for the first click, scroll or movement.

Left

Right

Middle

Back / Forward

0 · 0

Double-click

not yet

Polling

not measured

Pointer speed

not measured

Inside the stage the page asks the browser to prevent its context menu, side-button navigation, wheel autoscroll and page scrolling so the input check stays visible. Outside the stage these actions behave normally.

Buttonsevery one the browser reported
nothing clicked yet
Wheelscroll up and down inside the stage
nothing scrolled yet
Double-clickthis tool uses 500 ms and 10 CSS px
no double-click registered yet
Report ratehow often the pointer reports while moving
not measured yet: move the pointer across the stage
Pointer speedCSS pixels, with pauses of 50 ms or longer excluded
not measured yet: move inside the drawing area

Move the pointer across the stage to measure delivered movement events.

Pointer speed uses recent movement inside the drawing area, in CSS pixels per second. It is affected by system pointer settings, zoom and event delivery; it does not measure DPI, physical speed or hardware latency.

The five buttons a browser can name

A mouse can have any number of buttons; the DOM numbers five of them and reports anything else as a bare number with no agreed meaning. These numbers describe browser events, not your mouse's physical specification.

Button	Number	What it normally does
Left	0	the primary button
Right	2	the secondary button, which opens the context menu
Middle	1	the wheel pressed down
Back	3	the rear side button, which navigates back
Forward	4	the front side button, which navigates forward

Polling rate is a browser event estimate. Coalesced samples are included when the browser provides them. Animation-frame timing gives a comparison, not a measurement of the hardware display or mouse. Event rates cannot establish the cause of a low reading. Button and wheel counts describe delivered browser events. Click pairs use this tool's fixed timing and distance limits. Pointer speed uses CSS coordinates; event rate is a browser estimate. These do not measure DPI or hardware latency or establish a fault.

Common questions

How do I test mouse buttons, holds and scrolling?: Press each button inside the stage and watch its count and light. A held button stays lit until the page receives a release, cancellation or loss of focus. Scroll up, down or sideways to inspect wheel direction and travel. Move in the drawing area to leave a trail, or hold a button while moving to observe the hold and movement together. This is an input-event check, not a drag-and-drop target.
Why does right-clicking not open the context menu here?: The page prevents the context menu inside the stage so you can count right-button presses there. It also asks the browser to prevent wheel autoscroll, side-button navigation and page scrolling inside that stage. Outside the stage these actions behave normally; some browser or driver actions may still take precedence.
What is polling rate, and why does mine read 60 Hz?: Hardware polling rate is how often the mouse reports to the computer. This page instead estimates the rate of movement samples delivered by the browser, including getCoalescedEvents samples when available. Event merging, timestamp precision, motion, system load and browser scheduling affect the result. It compares the estimate with animation-frame delivery measured over at least half a second, not with a verified display specification. A value near 60 Hz can be consistent with frame-limited event delivery, but neither a low value nor a value above the frame rate proves the hardware rate or its cause.
What do the double-click and rapid-pair results mean?: This tool pairs non-overlapping left clicks that arrive within 500 milliseconds and 10 CSS pixels. It uses those fixed limits rather than reading your operating system settings or counting native dblclick events. A pair below 50 milliseconds is labelled a rapid pair. Press once deliberately, wait, and watch for unexpected extra presses; the event count can document what arrived, but timing alone cannot tell whether a switch, input software or an intentional clicking technique caused it.
Why do my back and forward buttons not show up?: The browser names side-button events as Back and Forward, button numbers 3 and 4. A driver may map a thumb button to a keyboard shortcut or another action instead, and browser navigation can take precedence. Extra button numbers are counted separately. A missing event does not establish that a physical button is absent or broken.
Does the wheel count work with a trackpad or Magic Mouse?: Yes, when the browser delivers wheel events. The counts are events in each direction, not physical wheel notches or individual gestures: drivers, smooth scrolling and trackpad momentum can produce several events for one action. Travel sums the reported deltas in CSS pixels, using 16 pixels for a line-mode unit and the window height for a page-mode unit. Pinch gestures delivered as Ctrl plus wheel are left to browser zoom and are not counted.
What does the mouse speed test measure?: Pointer speed is the recent path length divided by the time between captured movement samples inside the drawing area, in CSS pixels per second. The path retains up to 4,000 samples, breaks when you leave the area, and excludes intervals of 50 milliseconds or longer. System pointer speed, acceleration, browser zoom and sample delivery affect it. It is a screen-pointer measurement, not physical hand speed, mouse DPI or a click-speed score.
Can this test mouse DPI, sensor accuracy or hardware latency?: No. A page receives pointer coordinates after the device, driver and browser have processed them. DPI needs verified sensor counts and physical distance; hardware latency needs a physical timing reference. The trail can show the pointer path you observed, including visible jumps or drift, but cannot isolate a sensor fault, acceleration or delay. The tool does not calibrate the mouse or change sensitivity settings.
Can I test a gaming, wireless, Logitech, Razer or vertical mouse on a Mac or laptop?: A connected mouse can be checked here when its browser reports the button, wheel and movement events. The same applies to a laptop touchpad and a mouse connected to an Android device. A finger or pen is ignored. Model-specific buttons, battery level, wireless signal strength and device software features are not exposed by this test.
Does anything leave my computer?: The event records used by the test stay in this browser tab. They are not uploaded or saved between visits. Reset clears the recorded counts and trail, and reloading starts again.

Button and wheel counts describe delivered browser events. Click pairs use this tool's fixed timing and distance limits. Pointer speed uses CSS coordinates; event rate is a browser estimate. These do not measure DPI or hardware latency or establish a fault.