Pages Per Session
Pages per session (or screens per session for mobile) measures how many distinct pages or views a user visits in a single session. For content-heavy products, higher pages per session usually indicates stronger engagement and discovery. For task-focused tools, it may indicate confusion or inefficient navigation. Like session duration, the target value depends entirely on your product's intended UX.
Note: For single-page apps, track "screen views" or "virtual pageviews" using custom events. Raw pageview counts are meaningless without session counts.
Content/media sites: > 4 pages/session; B2B SaaS: 3–7 pages/session for task completion flows
< 1.5 pages per session on a multi-page product indicates most users are leaving from the landing page
Benchmarks by segment
How to improve Pages/Session
Improve internal navigation and cross-linking between related content or features to encourage continued exploration
Use in-context suggestions ("users who did X also did Y") to surface relevant next steps
Ensure your information architecture is logical — if users can't find what they need, they leave rather than browse
Reduce bounce rate from entry pages by ensuring the page delivers on the promise of the link that brought users there
Common measurement mistakes
Tools for measuring Pages/Session
Best-in-class behavioral analytics with powerful event segmentation, funnel analysis, and retention charts that go far deeper than Google Analytics
Best-in-class event-based analytics with intuitive funnel, retention, and flow reports that surface actionable insights quickly
Best-in-class autocapture technology — captures every click, scroll, and interaction without manual event tagging, enabling retroactive analysis on historical data
All-in-one product analytics platform combining analytics, session replay, feature flags, A/B testing, surveys, and a data warehouse — replacing multiple point solutions
Autocapture eliminates the need for manual event instrumentation — every click, pageview, and form interaction is tracked automatically from day one
All-in-one platform combining feature flags, A/B testing, product analytics, session replay, and web analytics — eliminating the need for separate tools
Frequently Asked Questions
No — it depends on your product type. For a content site, higher is better. For a task-focused SaaS, 3–5 pages to complete a workflow is efficient; 15 pages may indicate users are lost. Benchmark against your own task flows, not general benchmarks.
They're inversely related. A high bounce rate (users leaving after one page) mathematically lowers pages per session. Improving bounce rate on entry pages is the fastest way to improve pages per session. Fix the highest-traffic entry pages with the worst bounce rates first.