How the wheel diagnostic works
The protocol runs four short phases — down and up at your normal pace, then down and up at a controlled faster pace. Declaring the direction before each phase is the whole point: it lets the report distinguish an event that disagreed with your intent from one that simply followed a change of mind mid-stroke. A phase that receives too few events to judge is marked inconclusive rather than scored.
Everything is measured from browser WheelEvent data: direction per event, the reported delta and its unit, and the interval between consecutive events. Nothing is converted into physical notches, because a browser genuinely cannot see them.
The three patterns worth retesting
Reversals inside a phase
Events travelling opposite to the direction you declared. A handful mid-stroke suggests a dirty or worn encoder; every event flipped means a natural-scrolling setting, not a fault.
Gaps and dropouts
Long intervals inside a continuous stroke. Debris in the encoder slot, a failing sensor, or a wireless link on a weak battery all produce this shape.
Burst delivery
A pause followed by a clump of events with near-zero intervals. Usually the page or the system coalescing input under load rather than the mouse itself — retest on a quiet tab.
Isolate the fault before you replace anything
- Repeat the same protocol, same duration, same declared input category at least three times. A single odd run is noise; a repeated pattern is evidence.
- Retest in a second browser. Event coalescing and extension behaviour are per-browser; a hardware fault is not.
- Move to another USB port, and for a wireless mouse swap the battery and move the receiver closer before drawing conclusions.
- Try the mouse on another computer. If the pattern travels with the mouse, it is the mouse.
- Check your buttons and polling while you are here with the mouse test, which covers double-click chatter and polling rate.
The full symptom-by-symptom walkthrough lives in the scroll wheel troubleshooting guide, and the methodology page explains exactly what the classifier does and does not claim.
Wheel works, but you want a number?
If the diagnostic comes back clean and you are really here to find out how fast you can scroll, the scroll speed test starts the moment you hover it and reports pixels per second with a rating tier, and the scrolls per second test reports the SPS figure used across the click-speed category.
Mouse wheel test questions
Run the guided protocol above: four short phases, scrolling down then up at a normal pace and then a faster one. A healthy wheel produces a steady stream of events in the direction you declared. Reversals inside a declared phase, long gaps in the middle of a continuous stroke, or a phase with far fewer events than its twin are the three patterns worth retesting. Confirm any of them in a second browser before deciding the hardware is at fault.
A consistent flip in every phase is almost always a setting. macOS ships “natural” scrolling on by default; Windows exposes a per-device flip through a registry value that several mouse utilities toggle. An intermittent reversal — a handful of events going the wrong way inside an otherwise clean stroke — is different, and usually means a dirty or worn optical encoder in the wheel assembly.
Skipping shows up as unusually long gaps between events, or as a burst of events after a pause. The common causes are debris in the encoder wheel, a failing encoder, a wireless mouse on a low battery, or a page that is simply too busy to process input smoothly. The report separates inter-event gaps from burst delivery so you can tell an input problem from a rendering one.
No, and any tool that claims otherwise is overselling. A browser can only see events that reached the page — it is blind to a physical movement that produced no event at all, and software between the wheel and the page can reshape timing. What this test does give you is a repeatable observation you can compare across browsers, ports and machines, which is what actually isolates a hardware fault.
Power the mouse down, then rotate the wheel slowly while directing short bursts of compressed air into the gap on both sides of the wheel — that is where the encoder slots sit. A cotton swab very lightly dampened with isopropyl alcohol clears the wheel rim itself. Let it dry fully before reconnecting, and retest with the same protocol and duration so the two runs are comparable.
This page is a diagnostic: it asks you to scroll in a declared direction so it can judge whether the events matched your intent, and it reports direction, timing and delta units rather than a score. The scroll speed test is a benchmark: no setup, no declared direction, one big number. Use this page when something feels wrong, and that one when you want to know how fast you are.