Short answer: if your mouse wheel scrolls the wrong way, a software setting can explain it — check your operating system first (Windows Scrolling direction, or macOS Natural scrolling) and toggle it back. If instead it jumps or skips lines, that can be consistent with wheel encoder trouble or a units/driver issue. The scroll wheel test shows you, in the browser, whether wheel events go the direction you did not choose and whether pixel, line, and page units are mixing — but it reads browser wheel events, not physical wheel notches, so it cannot measure polling rate, DPI, or the encoder itself.
First, rule out the OS or driver setting
A wheel that consistently scrolls the opposite way can indicate a reversed setting. Rule that out before you suspect the hardware:
- Windows — open Settings › Bluetooth & devices › Mouse and check Scrolling direction. A mouse utility such as Logitech Options+ or Razer Synapse can also invert scrolling, so check it too.
- macOS — open System Settings › Mouse (or Trackpad) and toggle Natural scrolling. It is on by default and reverses the direction many mouse users expect.
- Then retest. Toggle the setting, then scroll again. If the direction is fixed, that is consistent with a setting-related cause.
Then confirm it in the browser
Open the scroll wheel test and scroll in one direction. The check counts wheel events whose vertical movement opposes the direction you chose, and it keeps pixel, line, and page units separate because they are not interchangeable. In browser terms that unit is the wheel event’s deltaMode: 0 is pixels, 1 is lines,2 is pages. Pause between runs, because touchpad or high-resolution momentum can carry a few events past the point where you stopped and look like a stray reversal.
For the exact counting rules and a sourced comparison of notches, Windows wheel units and browser deltas, read what scroll speed tests and their units actually mean.
Wrong way vs jumping — what each points to
- Consistent wrong way — can indicate a reversed or “natural” scrolling setting in the OS or a mouse utility. Retest after changing that setting.
- Occasional opposite-direction events — can come from an encoder misreading a notch, from touchpad momentum carrying past a pause, or from a driver quirk. Repeat with clean pauses; if it only happens sometimes, record it as an intermittent observation, not a fault verdict.
- Jumps or skips several lines — can be consistent with a units mismatch (a page or line event where you expected pixels), a driver set to scroll multiple lines per notch, or a worn or dirty encoder sending extra pulses.
What the browser can and cannot see
The wheel test reports aggregate browser wheel event counts, opposite-direction counts and signed totals grouped by deltaModeunit. These can show input opposing your selected direction or more than one unit group in a run; they do not show each event’s amount or timing. It does not see the physical wheel notches, the polling rate, the DPI, or the encoder hardware, so it cannot diagnose those. If you have seen a page claim to read those numbers, the honest limits are in what a browser reports when you think it is measuring polling rate and what a DPI analyzer web page really measures.
If the setting is not the problem
If reversed scrolling is off and the wheel still goes the wrong way or jumps, work through the hardware: blow out the wheel slot, try a different USB port, and test the mouse on another computer to separate the mouse from your driver. If it misbehaves everywhere and it is still under warranty, the browser record of opposite-direction counts and totals by unit is the same kind of reproducible evidence covered in how to prove a mouse fault for a warranty or RMA claim.