Can this tool measure DPI or polling rate?

No. Browsers do not expose DPI, polling rate, sensor accuracy or switch debounce, so the tool only reports button, wheel and pointer events the browser observes.

Why does my back or forward button not register?

Some browsers, operating systems or mouse drivers handle the back and forward buttons before the page receives them, or remap them. The tool asks the browser not to navigate inside the test area, but it cannot override driver behaviour.

Does a short double-click interval mean my mouse is broken?

Not by itself. A very short interval between two left presses can point to switch chatter, so repeat the check, try another browser and compare with another mouse before drawing conclusions.

Mouse Tester

Runs locally in your browser

Check mouse buttons, wheel, double clicks and CPS in your browser

Click, scroll or press side buttons inside the test area.

Test area

Click, hold, scroll and press side buttons here

Not tested
Pressed now
Observed

Back and Forward can still navigate on some browsers or mouse drivers. Inside the test area the tool asks the browser not to.

Results

Total clicks

0/5

Buttons observed

Wheel events

Buttons

Leftbutton 0Not testedPresses: 0
Middlebutton 1Not testedPresses: 0
Rightbutton 2Not testedPresses: 0
Backbutton 3Not testedPresses: 0
Forwardbutton 4Not testedPresses: 0

Wheel

Up events: 0
Down events: 0
Last deltaY: —

Each count is one browser wheel event, not one physical wheel notch.

Last event: No events yet
Pointer position: —

CSS pixels from the top-left corner of the test area.

Diagnostics

Buttons bitmask: 0b00000 (0)
Pointer type: —
Wheel delta unit: —
Events in session: 0

Bits from low to high: left, right, middle, back, forward.

Double-click check

Double clicks

—

Last interval

—

Shortest double click

Measured between left presses in the test area. A short interval alone does not prove a faulty switch.

Advanced

Double-click window500 ms

Two left presses within this time count as one double click.

CPS test

Duration

Click here to start

The timer starts on your first left click and counts only left clicks inside the area.

5.0 s

Remaining

Clicks

0.00

CPS

—

Best this session

Runs locally in your browser. Input events are not stored or sent.

Shows browser-observed events only. It does not measure DPI, polling rate, sensor accuracy or switch debounce.

Keyboard TesterCheck every key on a physical keyboard in your browser Device & Browser InformationSee what your browser exposes for support and debugging Fullscreen Background & Screen TestFill your screen with a color, gradient, image, monitor test pattern or gentle screensaver

What Mouse Tester checks

Mouse Tester shows which mouse inputs your browser actually receives: left, middle, right, back and forward buttons, wheel up and down events, the time between left presses and your clicks per second. Use it after cleaning or replacing a mouse, when a button seems to double-click by itself, or when a side button does nothing in an app.

How to use it

1.Move the pointer into the test area.
2.Press each button and scroll the wheel up and down; tested buttons change from Not tested to Observed.
3.Watch Pressed now while holding a button to spot stuck or chattering presses.
4.Use the Double-click check and its interval readout to see how close two left presses were.
5.Choose a CPS duration and click the CPS area to start a timed run.
6.Select Reset to start a new session.

Reading the results

Counts come from browser PointerEvent, MouseEvent and WheelEvent data. A wheel count is one browser wheel event, which may differ from physical notches on smooth or high-resolution wheels. A very short interval between two left presses can point to switch chatter, but the tool never declares hardware faulty: repeat the check, try another browser and compare with another mouse.

Limits and privacy

Browsers cannot report DPI, polling rate, sensor tracking accuracy or switch debounce, so this tool does not claim to measure them. Some browsers, operating systems or mouse drivers handle Back, Forward or Middle buttons before the page sees them. Everything runs locally in your browser; no input events are stored or sent.