Section 1
Scroll-wheel test
Scroll over this area to test the wheel
Press Start to begin. The page scrolls normally until testing starts.
Latest direction
—
Total scroll events
0
Possible reverse jumps
0
Current expected direction
Auto
Recent direction history (newest first)
Scroll event log
Newest first · latest 40How to test
- Select the expected direction or leave it on Auto.
- Move the mouse over the test area.
- Scroll steadily in one direction.
- Try several controlled reversals.
- Watch the event log for possible reverse jumps.
A reverse jump is only a browser-observed pattern. Intentional scrolling can produce the same result.
Section 2
Mouse-button switch test
Left
Total presses
0
Press interval
—
Middle
Total presses
0
Press interval
—
Right
Total presses
0
Press interval
—
Possible switch-bounce faults
Same-button presses < 80 ms apart
0
Button event log
Newest first · latest 40A press interval below 80 ms may indicate possible switch bounce, but a very fast intentional press can trigger the same warning. This result does not prove that the switch is defective.
Keyboard activation is not counted as a physical mouse press. The right-click menu is suppressed only inside the right-button zone while testing.
How to test
- Click the appropriate test zone with the corresponding mouse button.
- Repeat several presses at normal speed.
- Try controlled rapid presses.
- Watch the press interval and warning counter.
- Repeat the test several times for consistency.
Section 3
Approx. mouse event rate
Current rate
Movement state: Idle0 events per second
Approx. browser-delivered mousemove events in the last ~1 s · updated 5× per second
Press Start, then move the mouse over the page.
Peak rate
Highest observed rate
0 events/s
Movement events
Counted this session
0
This is an approximate browser-reported mouse movement event rate, not a confirmed hardware polling rate. Browsers may coalesce, limit, or otherwise process mouse events differently from the device's actual hardware report rate.
Movement is measured only while this page/window can receive mouse events.
How to test
- Move the mouse slowly around the page.
- Move it continuously for several seconds.
- Try faster movements.
- Watch the approximate event rate and peak rate.
- Stop moving and confirm the monitor returns to Idle / 0 events/s.
Session summary
All data stays in this browser tab. Nothing is uploaded.
- Test status
- Ready
- Scroll events
- 0
- Possible reverse jumps
- 0
- Left presses
- 0
- Middle presses
- 0
- Right presses
- 0
- Possible switch-bounce faults
- 0
- Approx. movement rate
- 0 events/s
- Peak movement rate
- 0 events/s
Common questions
What does this mouse test check?
It records browser-received scroll-wheel directions, mouse-button press intervals, and pointer-movement events. It highlights patterns that may be worth checking, but it cannot confirm that your mouse is faulty.
Does the movement rate show my mouse's real polling rate?
No. The number is an approximate count of movement events delivered by your browser each second. Browsers can combine or limit events, so it does not confirm the mouse's hardware polling rate.
Does a reverse jump mean the scroll wheel is broken?
Not by itself. A deliberate change of direction can look similar. In Auto mode, the tool flags a brief reversal followed by a quick return to the previous direction; repeat the test while scrolling steadily.
Does a button press under 80 ms prove a switch fault?
No. The tool marks same-button presses less than 80 ms apart as a possible switch-bounce pattern. A fast intentional press can trigger the same warning.
Are my mouse clicks and movements uploaded?
The test code keeps its counts and event logs in this browser tab and does not send them to a testing API. The page does load Tailwind CSS from its CDN to style the interface.
Can I use the tests on a phone or touchpad?
The button test needs a physical mouse. Touchscreens and touchpads may behave differently and are not equivalent to a mouse switch or scroll-wheel encoder.
Measurement limitations
- Browser mouse events are only received while the page/window can receive them.
- Browsers can coalesce or limit mouse events, often aligning them to display refresh.
- The movement-rate measurement is an approximation and does not confirm hardware polling rate.
- Very fast intentional clicks can trigger the switch-bounce warning.
- Intentional scroll-direction changes can trigger reverse-jump detection.
- Touchpads and touch devices may behave differently from physical mice.
- This tool cannot read USB polling rate, firmware state, or the physical condition of switches and encoders.
- Results describe possible input issues only and are never a confirmed hardware diagnosis.