Features › Goals and missing pages › Scroll depth and page speed

Scroll depth and page speed

How far people read. How fast it loads.

Visitors tell you a post was opened. Scroll depth tells you it was read. Page speed tells you whether it loaded quickly enough for people to stay. ReaderCount measures both from your real readers, on their own phones and computers.

Start your 30-day trialTry the live demo

The Page Speed tab: on phones, loading 2.9 seconds, rated Needs attention; on computers, 1.6 seconds, rated Good; then each page, with Kindle colorsoft review at 4.6 seconds marked Requires fix

What you get

All three are tabs on the Reader Engagement & Page Speed card.

  • Scroll Depth: how far down each page people typically read, how many got halfway and how many reached the end
  • Page Speed: Google’s Core Web Vitals from your real readers, on phones and on computers, rated Good, Needs attention or Requires fix
  • Form Drop-Off: how many people started each form and how many sent it
  • No setup, no extra script, and nothing that could follow a reader

Scroll depth

The Scroll Depth tab: Fastmail review read to a typical 66%, with 80% halfway and 45% to the end; Kindle colorsoft review only 37%, with 33% halfway
FigureWhat it means
Typical depthHow far down the page readers got, on average.
HalfwayThe share of readers who got at least halfway down.
To the endThe share who got to the last tenth of the page.

What to look for

  • Few readers halfway: the opening isn’t holding them. Answer the question sooner and cut a long introduction.
  • Many halfway, few to the end: the post may be longer than it needs to be, or the end isn’t worth reaching. Move your best advice and links higher.
  • Most to the end: readers want more. Give them a next post to read and a sign-up box at the end.

Page speed

ReaderCount measures Google’s three Core Web Vitals in your readers’ own browsers, on the first page of each visit:

Shown asGoogle’s nameGoodRequires fix
LoadingLargest Contentful Paint (LCP): how long the main content takes to appear2.5 s or lessOver 4 s
ResponseInteraction to Next Paint (INP): how quickly the page reacts to a tap or click200 ms or lessOver 500 ms
Layout jumpsCumulative Layout Shift (CLS): how much things move about while loading0.1 or lessOver 0.25

Anything in between is Needs attention, and each page is rated by its worst figure. Like Google, ReaderCount shows the speed for 3 in 4 readers, so a page is only Good if it’s good for most people, not just on average.

The top of the tab gives your whole website on phones and on computers, because phones on mobile data are usually much slower. Under that, each page with its own figures and how many visits were measured.

Why real readers? Speed tests run on one fast computer. Your readers use old phones, busy trains and slow Wi-Fi. These are the figures Google looks at too.

Making a slow page faster

  • Slow loading: usually the first big picture. Make it smaller, use a modern format such as WebP, and make sure it isn’t set to load lazily.
  • Slow response: usually heavy scripts, such as ads, chat widgets or sliders. Remove what you don’t need, or load it later.
  • Layout jumps: give pictures, adverts and embeds a fixed width and height so the page doesn’t move as they load.

Pages slower than 4 seconds for 1 in 4 readers also show in Site Health, and a slow page that people leave straight away shows in What to fix.

Form drop-off

The Form Drop-Off tab: the contact form, started 120 times and sent 34 times, 28%, marked Many give up; Newsletter sign-up, started 286 times and sent 177, 62%

When a reader starts filling in a form, ReaderCount notes the form’s name. When they send it, that counts too. A form that 10 or more people started and fewer than 30% sent gets a Many give up label.

ReaderCount never sees what anyone types. Forms use the same name as their goal, so name a form with data-rc-goal and both use that name.

The fine detail

Enough readersA page needs at least 5 measured visits before its scroll depth or speed is shown.
First page onlySpeed is measured on the first page of each visit, where a slow page loses the most readers.
Monthly allowanceForm reports share the problem allowance: 20,000 a month on Solo, 200,000 on Business.
PrivacyJust numbers for each page: no recordings, no mouse movements, nothing anyone typed.
PlansIncluded on every plan and in the 30-day trial. See plans and prices.

Questions

Does measuring speed slow my pages down?

No. The figures come from the browser’s own measurements, and are sent with the time on page as the reader leaves.

Why are my figures different from PageSpeed Insights?

PageSpeed Insights runs a test from one machine, or shows Google’s figures for the last 28 days. ReaderCount shows your own readers for the dates you choose.

Why is a page missing from the list?

It needs at least 5 measured visits in the dates you chose. Choose a longer date range to see quieter pages.

Is this a heatmap or session recording?

No. ReaderCount keeps how far down the page each reader got, as a number. Nothing that could replay or follow a reader.

Can I see what people typed before they gave up on a form?

No, and nor can anyone else. ReaderCount only knows the form was started and whether it was sent.

Still have a question? Get in touch and we’ll help.

More ReaderCount features

See every feature

Write it. Speed it up. Watch them read.

Add one line to your site and your first visitors appear within seconds. No cookies, no banner, no personal data.

Start your 30-day trialSee plans and prices

No card needed. Then from £9 a month. Try the live demo first if you like.