Short answer: scrolling that feels choppy or stutters is almost always software — a smooth-scroll setting, a heavy or janky page, or the browser’s own rendering — not a failing mouse. Scrolling that misses steps, where a notch you clearly felt produces no movement, points more at the wheel encoder. Rule out the software causes first, then open the scroll wheel test to see whether wheel events arrive evenly or with gaps. Keep in mind the test reads browser wheel events, not physical wheel notches, so it can confirm the symptom but cannot measure polling rate, DPI, or the encoder itself.
First, separate “choppy” from “missing steps”
These two symptoms feel similar but have different causes, so name yours before you chase a fix:
- Choppy or stuttering — the page moves, but not smoothly. It lurches, lags a frame, or judders. This is a rendering or setting problem far more often than a hardware one.
- Skipping or missing steps — you feel a detent click but nothing scrolls, or it occasionally jumps the wrong amount. This is the pattern that points at the encoder or a dirty wheel.
Rule out software: smooth scrolling and the page
Most stutter lives here, so clear it before you suspect the mouse:
- Try a different app and page. If a plain page or a text editor scrolls smoothly but one heavy website stutters, the site — not the mouse — is the cause. Background tabs and a busy CPU do the same thing.
- Toggle smooth scrolling. Browsers and some mouse utilities add animated “smooth” scrolling that can look like a stutter on a slow frame. Turn it off (in the browser’s settings, or in Logitech Options+ / Razer Synapse) and retest.
- Check the basics. A near-full battery-saver mode, an outdated GPU driver, or a very high refresh-rate display fighting a heavy page can all read as scroll jank. Fix those and much “wheel” stutter disappears.
Then check the wheel in the browser
Open the scroll wheel test and roll the wheel slowly, one detent at a time. Watch whether every notch you feel produces an event and whether the amounts are even. Even, one-per-notch events with the occasional larger value from momentum are normal; a felt notch that produces no event, repeatably, is the signal that matters. The test keeps pixel, line, and page units separate — in browser terms the event’s deltaMode (0 pixels, 1 lines, 2 pages) — because a driver switching units can also look like uneven scrolling. Pause between runs so touchpad-style momentum does not add stray events.
Stutter vs skipped steps — what each points to
- Smooth in the test, choppy only on some pages — software and rendering. The mouse is fine; the page, the browser, or the smooth-scroll setting is doing it.
- Felt notches that produce no event, repeatably — the encoder is misreading. On many mice this is dirt or wear in the wheel encoder; cleaning sometimes helps, but a consistently dead notch is a hardware fault.
- Occasional wrong-amount or wrong-direction events — more of a units or direction issue; our guide on a mouse wheel that scrolls the wrong way or jumps covers that separately.
What the browser can and cannot see
A web page sees only the wheel events your system sends it, after the OS and driver have processed them. So the scroll wheel test can show you that a notch produced no event, or that units are mixing — a real, repeatable symptom you can act on. What it cannot do is measure the wheel’s polling rate, its DPI, or the encoder’s mechanical condition; none of those are exposed to a browser. Anything claiming to read them from a web page is inferring, not measuring. For the same reason a page cannot truly read a polling rate.
If it is the encoder
Once software is ruled out and the test shows felt notches with no event, treat it as hardware. Blowing out or cleaning the wheel encoder resolves some cases; a wheel that skips the same way after cleaning is failing. If the mouse is in warranty, capture the repeatable symptom — a short screen recording of the test with no event on a felt notch — the same way you would build evidence for any warranty or RMA claim.