Reading behaviour
What scroll depth tells you about a page
If many visits reach halfway down a page but few reach the bottom, you have a clue about where people stop moving. You do not yet know whether they found their answer, got bored or clicked away. Scroll depth becomes useful when you connect it to the page’s purpose.
Start with the action the page is meant to support
Take a service page with a phone link near the top and a long FAQ below. A visitor who calls after reading the first screen may have done exactly what you hoped. Low scroll depth on that visit is no failure. On a guide that promises a worked example near the end, the same pattern might suggest the example is too hard to find.
Write down one question before opening the chart: Can visitors find the next useful step? Then locate that step on the page. Is the price, answer, form or contact link above or below the depth where visits tend to stop?
Know what the percentage measures
Scroll depth is how far down the document a browser has reached, expressed as a percentage of the page’s height. It is not a measure of reading, attention or satisfaction. A fast swipe can cross several milestones without a word being read. Screen height matters too: on a short page, much of the content may already be visible without any scrolling.
Tools collect it differently. Google Analytics’ enhanced measurement scroll event fires when 90% of a page first becomes visible. TrafficWisp records 25%, 50%, 75% and 90% milestones when a visitor scrolls. Its reading-depth report shows the share of recorded visits reaching each milestone. It does not record time spent reading each section, and a page loaded without a scroll may have no milestone even if its content fits on screen.
Compare the drop with the page itself
Suppose 100 visits reached a long landing page, 68 recorded 50% depth and 24 recorded 75%. Open the page on a phone and a laptop. What sits between those points? If the main answer is buried after repeated introductory sections, move it earlier and make the heading clearer. If the section is a detailed FAQ for people who need it, that drop may be entirely reasonable.
Check whether people took an action before leaving. A telephone or button click is a stronger sign of intent than reaching the footer, though a click alone does not prove a call connected or a form was completed. Look at the next page in the visitor journey as well. Someone who leaves a pricing page for a contact page may be progressing, even if their scroll was shallow. TrafficWisp’s product overview describes its page activity, anonymous journeys and tracked interactions.
Make one page change you can assess
If the useful answer or action sits below the point where many visits stop, bring it closer to the top. Keep the rest of the page available for people who need detail. Note the change date, then compare similar periods for the same page and device mix. Look for more relevant clicks or onward visits, not just deeper scrolling. A shorter, clearer page can lower a scroll percentage while helping more people.
If visits are scarce, avoid a verdict from a handful of milestones. First check that tracking is installed, the page receives visits and the action you care about is measurable. If the problem begins before the visit, our guide to Search Console impressions without clicks covers that separate question.
See the step after the scroll
TrafficWisp is in private beta. Request access to see reading depth alongside page journeys and useful interactions.
Request beta access