Time to next page: how long people stay before moving on
It works without the engagement add-on.
For each page, how long people stay before opening the next page, and how often they leave from it.
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
quietstats measures the time from each pageview to the next pageview in the same visit, and shows for each page the typical (median) time, the slow quarter and the share of views that were the last in the visit.
Why it matters
It works without the engagement add-on. Short times on long pages suggest people skim; long times on simple pages suggest something is confusing.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Content, tap Time to next page. You can also search for it on the All reports screen.
- Pick a date range (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, events, goals or daily totals 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
- Pages followed by another page fewer than 5 times are hidden
- The last page of a visit has no time, so it counts as an exit
- 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
How is this different from Time on page?
Time on page uses engaged time from the add-on. This uses only the gap between pageviews, so it works for every site.
Does it store anything new?
No. It is worked out from the pageviews and events you already have when you open the screen, and only the totals are kept for 10 minutes.
Related features
Behaviour and contentScroll depth and engaged time
Behaviour and contentExit pages and where visitors went next
Behaviour and contentPages with traffic: how much of your site earns visits
Behaviour and contentPages that lead to search: where content falls short
Behaviour and contentCompeting pages: pages that may split the same searches
Behaviour and contentPage importance: the pages that hold your site together
Behaviour and contentPrivacy proof page and badge for your site
Privacy and performance
All behaviour and content features → · All features → · Docs: Time to next page 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.