How fast can you scroll?
Two numbers answer that question and they are not interchangeable. Pixels per second is distance: how far the page actually moved. It is the figure that matches the everyday sense of “fast scrolling”, and it depends as much on your operating-system settings as on your hand. Scrolls per second is input rate: how many wheel events your browser received. It is closer to a measure of you rather than your configuration, which is why it is the number the wider click-speed community compares.
This test reports both from the same run, plus the best single second of the run, so a long window does not punish you for pausing. Start with the 10-second window — long enough to be repeatable, short enough that your forearm is not the limiting factor.
Scroll speed rating scale
Tiers are for distance, in CSS pixels per second. A 1,000 px/s run moves roughly one laptop screen height every second.
| Tier | Range | What it means |
|---|---|---|
| Slow | 0–599 px/s | Under about half a laptop screen height per second. |
| Normal | 600–1,499 px/s | Roughly one to two screens a second — ordinary browsing. |
| Fast | 1,500–3,499 px/s | Skimming pace. Several screens a second. |
| Very fast | 3,500–7,499 px/s | Hunting for the bottom of a long page. |
| Extreme | 7,500+ px/s | Free-spin wheel or a high-momentum touchpad flick. |
Prefer the event-rate view? The scrolls per second test uses the same engine with the SPS scale in front, and average scroll speed explains where these boundaries come from.
Get a faster score without fooling yourself
- Free-spin beats ratchet. If your mouse has a wheel-release button, disengaging the detents removes the mechanical ceiling entirely — a released flywheel keeps emitting events after your finger has left it.
- Raise lines-per-notch, not effort. Windows (Settings → Bluetooth & devices → Mouse) scrolls three lines per notch by default. Raising it multiplies your pixels per second without changing your input rate at all, which is exactly why the two metrics are reported separately here.
- Use the whole finger travel. Short fingertip taps on the wheel waste most of the stroke. Longer pulls from the second joint keep the wheel moving between strokes.
- Pick one duration and stay on it. A 5-second score is not comparable with a 60-second score. Track one window across days instead of chasing a single lucky burst.
- Stop if it hurts. Rapid repetitive wheel flicking strains the same tendons as jitter clicking. No score is worth that.
What a slow score can actually mean
A score far below your usual figure is worth a second look before you blame technique. A worn or dirty wheel encoder drops events, which shows up as a low event count next to a normal-looking distance, or as visible stutter in the run. A wireless mouse on a failing battery reports in bursts. Heavy browser extensions can throttle event delivery on a busy page.
If any of that sounds familiar, run the mouse wheel test — it uses a guided up/down protocol and reports reversals, gaps and bursts instead of a single headline number — and then work through the scroll wheel troubleshooting guide.
Scroll speed test questions
Ordinary browsing runs at roughly 600–1,500 CSS pixels per second. Skimming a long page sits between 1,500 and 3,500 px/s, a fast deliberate flick reaches 3,500–7,500 px/s, and a free-spin wheel released at full speed can exceed 7,500 px/s. In scrolls per second — wheel events rather than distance — 4–7 is normal, 8–12 is fast, and above 21 usually means a free-spin or high-resolution wheel.
The box you scroll is a real overflow container, so the browser reports exactly how far it travelled in CSS pixels. Speed is that distance divided by the measured window. Nothing is converted from WheelEvent.deltaY, which means a mouse that reports lines rather than pixels is measured just as accurately as one that reports pixels.
Distance per notch is an operating-system setting. Windows scrolls three lines per notch by default and lets you change it to anything from one line to a full page; macOS applies acceleration so a fast wheel travels further per notch than a slow one; browsers then apply their own line-height maths. Same hand, same mouse, different machine, different pixel total — which is why this test also reports scrolls per second, which is far less sensitive to those settings.
It is the highest distance recorded in any single second of your run, found by sliding a one-second window across every recorded sample. A 30-second run averages out your pauses; the burst figure shows the ceiling you actually hit. Competitive scroll scores are usually burst numbers, not averages.
Yes, and trackpads usually score higher than mice. A two-finger flick produces a long tail of momentum events after your fingers leave the surface, so both the distance and the event count keep climbing for a moment. That is genuine scrolling as far as the page is concerned — just be aware you are not comparing like with like against a detented wheel.
You can. Swiping the box moves it for real, so distance and pixels per second are exact. Touch input produces no wheel events, so scrolls per second is shown as a dash rather than as zero — the tool reports what it could not observe instead of pretending the value was nil.