Reading quadrant: read, skimmed, stuck or missed
One number per page hides why it works or not.
Every page plotted by scroll depth and engaged time against your own medians, sorted into four groups with a fix for each.
Why quietstats: you get this without cookies, a consent banner or storing IP addresses, in every plan including Free.
In every plan, including Free. Behaviour and content.
📘 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 data-engage measurements, quietstats plots each page with 10+ measured views by average scroll depth (across) and median engaged time (up). Your site’s medians split the chart into Read (far and long), Skimmed (far but quick), Stuck (long but shallow) and Missed (short and shallow), with a table for each.
Why it matters
One number per page hides why it works or not. The quadrant tells you what to do: make the point stand out, fix what holds people up near the top, or rethink the promise.
How it works
- Open your dashboard, go to Deep dives and scroll to Analysis lab.
- Under Content, tap Reading quadrant.
- 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 data-engage on your script tag; pages need 10+ measured views
- 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
Why compare with my own medians?
A recipe and a contact page are read differently. Comparing your pages with each other gives fairer, more useful groups.
What if I see nothing?
Add data-engage to the quietstats script tag; measurements start with the next visits.
Related features
Behaviour and contentPage deep dive: everything about one page on one screen
Behaviour and contentLanding page scorecards: an A to F grade for every landing page
Behaviour and contentSite sections: your site as a folder tree
Behaviour and contentBack-and-forth pages: returns and detours
Behaviour and contentTraffic concentration: how much depends on a few pages
Behaviour and contentPages read together: pairs and “read next” ideas
Behaviour and contentCountry quadrant: where to grow
See your traffic
All behaviour and content features → · All features → · Docs: Reading quadrant 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.