Keyboard Tester / Mouse button test
Mouse button test
Click, scroll and move the mouse inside the test box. Each button lights up on the mouse drawing while it is held and keeps a count, the wheel counts steps up, down and sideways, and the double-click panel shows the time between your two presses. A button that never lights or counts is not reaching the browser.
Click, scroll and move in this box. The right-click menu is switched off here.
Buttons
| Button | Clicks | State |
|---|---|---|
| Left | 0 | idle |
| Middle | 0 | idle |
| Right | 0 | idle |
| Back | 0 | idle |
| Forward | 0 | idle |
Wheel
- Up events
- 0
- Down events
- 0
- Tilt (horizontal)
- 0
- deltaY
- –
- deltaX
- –
- deltaMode
- –
Double-click
–
Time between the two presses of your last double-click.
Pointer events per second
move the mouse here
Peak: –. An estimate only: browsers may merge events to the screen refresh rate.
Event log
What each panel shows
The table lists the five buttons the browser can report: left, middle (wheel press), right, back and forward. Back and forward are the two side buttons many mice have; the browser numbers them 3 and 4. The State column says idle, pressed or tested, so you do not have to rely on the colour of the drawing.
The wheel panel counts events, not notches. A smooth-scrolling wheel can send many events per notch, so compare the counts with how much you actually scrolled. deltaY is the vertical amount, deltaX is sideways tilt, and deltaMode tells whether the browser counts in pixels, lines or pages.
Why the right-click menu and back button are off here
Inside the box the page blocks the context menu, the middle-click scroll mode and the browser’s back and forward action, so those buttons can be tested without leaving the page. Outside the box they behave as usual. If a side button still navigates back, your mouse driver may be sending a keyboard shortcut instead of a real button press, and the browser has nothing to report.
Pointer events per second
While you move the mouse the page counts pointer events over the last second. A mouse with a 1000 Hz polling rate can in theory send about 1000 position updates per second, a basic one about 125. Browsers often combine events to match the screen refresh, so a result near 60 or 144 usually shows the display rate, not the mouse. Treat the number as an estimate and use it to compare two mice on the same computer.
Which button is faulty?
If a single button gives no count, try the mouse on another computer. If it works there, the problem is software: a mouse utility remapping the button, or a setting for left-handed use. If it fails everywhere, the switch under it is worn. Clicks that register twice are better checked on the double click test, and a wheel that jumps backward on the scroll wheel test.
Questions people ask
How do I test my mouse buttons online?
Move the pointer into the test box and press each button. The matching part of the mouse drawing lights up while held and its row in the table counts the clicks. All five rows should reach at least one click if the mouse has all five buttons.
Why is my mouse back or forward button not detected?
Some mice send those buttons as keyboard shortcuts through their driver, so the browser never gets button 3 or 4. Others need the vendor software to be installed or the button assigned to its default action. Try the mouse on another computer to see whether it is the mouse or the software.
How do I know my mouse polling rate?
Move the mouse in circles inside the box and read the events per second. Browsers can merge events, so the page shows an estimate, often capped near your screen refresh rate. For an exact rate you need a dedicated tool outside the browser.
Why does my middle click not work?
The wheel press is a separate switch. If the wheel scrolls but the middle row never counts, the wheel button is worn or blocked by dirt under the wheel. If it counts here but not in an app, the app is not using middle click.