How the distance is counted
The track above is a real scroll container, so every pixel counted is a pixel the browser genuinely moved. Nothing is inferred from WheelEvent.deltaY, which means a mouse reporting lines instead of pixels is measured just as fairly as one reporting pixels, and a trackpad’s momentum counts exactly as far as it actually travelled.
The conversion is the CSS definition and nothing more: 96 px to the inch, 25.4 mm to the inch, so 3,779.53 px to the metre. Your monitor’s real physical pixel pitch is not involved — this is a distance in layout units, the same on a phone and on a 4K display.
- 10 m
- 37,795 px
- 50 m
- 188,976 px
- 100 m
- 377,953 px
- 500 m
- 1,889,764 px
Strategy, for whatever that is worth
- Release the ratchet. If your mouse has a free-spin mode, this challenge is what it was built for. One hard flick keeps the wheel turning — and the distance climbing — long after your finger has left it.
- Do not fight the momentum. On a trackpad, repeated hard flicks in the same direction stack momentum. Short choppy swipes cancel it.
- Keep the tab in front. A hidden tab stops delivering scroll events, so the run ends and is marked incomplete rather than quietly recording a window you never saw.
- Start at 10 m. It is the same physics in a tenth of the time, and it is a much better way to find out whether a technique is actually working.
- Take breaks. Sustained rapid wheel work strains the same tendons as jitter clicking. Stop if your hand complains.
Other ways to measure the same hand
If you would rather have a rate than a race, the scroll speed test gives pixels per second over a fixed window with a rating tier, and the scrolls per second test measures wheel-event rate instead of distance. For the button rather than the wheel, try the CPS test. And if the wheel feels wrong rather than slow, the mouse wheel test is the diagnostic.
100 meter scroll questions
It is a speed challenge: scroll a page 100 metres of real distance as fast as you can. Distance is counted in CSS pixels — the unit browsers actually use for layout — and converted at the CSS definition of 3,779.53 pixels to the metre. The clock starts on your first scroll and stops the instant you cross the line.
Exactly 377,952.76 CSS pixels. CSS defines one inch as 96 pixels and one inch as 25.4 mm, so a metre is 96 ÷ 0.0254 = 3,779.53 pixels. That is a layout unit rather than a measurement of your physical screen, so the same 100 m run covers the same pixel count on every display.
At an ordinary browsing pace of about 1,000 px/s the run takes around six minutes, which is why the shorter 10 m and 50 m goals exist. A determined detented-wheel run at 3,000–4,000 px/s finishes 100 m in roughly 100 seconds. Free-spin wheels and trackpad flicks routinely sustain 8,000 px/s or more and can break the minute.
A trackpad usually wins on raw distance because a single flick keeps travelling under momentum after your fingers lift. A free-spin mouse wheel is the strongest overall: releasing the ratchet turns the wheel into a flywheel that keeps producing scroll for a second or more per push. A standard detented wheel is the slowest, because each notch caps how far one step can travel.
It changes the answer, so it is worth being upfront about. Windows scrolls three lines per notch by default and lets you raise it to a full page, which multiplies distance per notch without changing your input rate at all. If you are comparing with a friend, agree on the setting first — or compare on the scrolls per second test instead, which measures event rate and is far less sensitive to it.
In your browser’s local storage, on this device only, under a key scoped to the distance goal you chose. There is no account, no leaderboard and no upload. Clearing site data removes it.