Speed vs engagement: do slow pages lose visitors?
Speed scores are abstract.
Pages grouped as fast, mixed or slow from real-visitor speed checks, compared on bounce rate and engaged time, with the slowest busy pages listed.
Why quietstats: you get this without cookies, a consent banner or storing IP addresses, in every plan including Free.
In every plan, including Free. Privacy and performance.
📘 Step-by-step guide, with screenshots and diagrams →
Start free, no cardSee live demo
- No cookies or consent banner
- No IP addresses stored
- Groups under 5 visitors hidden
- 845-byte script
- Free plan, no card


What it is
Using the optional speed add-on’s page totals, quietstats puts pages with 10+ speed checks and 10+ visitors into Fast (under 10% of LCP, INP and CLS checks poor), Mixed (10–25%) or Slow (over 25%). It compares each group’s bounce rate as a landing page and median engaged time, and lists the slowest busy pages first.
Why it matters
Speed scores are abstract. Seeing that slow pages also bounce more puts a real cost on the problem.
How it works
- Open your dashboard, go to Deep dives and scroll to Analysis lab.
- Under Content, tap Speed vs engagement.
- Pick 7, 30 or 90 days (and any options at the top), read the “How to read this” notes, and download any table as CSV.
Privacy: what is and isn’t collected
Collected
- Nothing new: it reads the pageviews (and goals, events or speed checks) you already have
Never collected
- Anything about a single visitor
- Links between days: visitor ids still reset at midnight
- Cookies, localStorage or anything else stored on the visitor’s device
- IP addresses or user agents (used in memory, then discarded)
- Anything that links a visitor across days (the visitor ID resets daily)
Rows and limits
- Needs the speed (vitals) add-on; pages need 10+ checks and 10+ visitors
- A gap is a lead to check, not proof: slow pages may attract different visitors
- Up to 92 days and 200,000 pageviews per screen
- Read from the database only when you open it, then kept for 10 minutes
“Rows” are database rows written, which is what our hosting is billed on. Reads are not rows written. Methodology →
Questions
What is a poor check?
A page load whose LCP, INP or CLS was in Google’s “poor” band.
Does this slow my site?
No. It only reads totals the add-on already sent.
Related features
Behaviour and contentUptime checks: know when your site was down
Behaviour and contentPage deep dive: everything about one page on one screen
Behaviour and contentHigh contrast and larger text: easier to read, everywhere in the app
Privacy and performanceFree tools: script size calculator and cookie banner checker
Privacy and performanceCompact mode: more on screen
Privacy and performanceHead-to-head comparison guides
Privacy and performanceConversion by engagement: scroll and time against conversions
Goals, events and conversions
All privacy and performance features → · All features → · Docs: Speed vs engagement guide → · Compare features with other tools →
Guides on this topic
Set it up
Nothing to set up: it works with the standard one-line script.
<script data-host="https://quietstats.co.uk" data-dnt="true" src="https://quietstats.co.uk/js/script.js" id="YOUR_SITE_ID" async defer></script>Try it on your own site
Free during launch: one site and 5,000 pageviews a month, no card needed. After launch, paid plans start at £5 a month.