Join the waitlist and get Sublim Business free for 3 months  Claim offer

Web Analytics

Pages per session: definition and interpretation

Guillaume Sallé
Guillaume Sallé
Analytics Content & Glossary Lead

Updated on February 22, 2026

Quick definition

Pages per session is the average number of pageviews viewed by a visitor during a single visit. It is a depth-of-engagement indicator that reflects the site's ability to hold attention and guide users through its content.

How it works

Formula

Pages per session = Total number of pageviews ÷ Total number of sessions

Example: 50,000 pageviews for 15,000 sessions in January → 50,000 ÷ 15,000 = 3.3 average pages per session.

Pages per session gives an immediate indication of the effectiveness of a site's navigation structure and internal linking.

Benchmarks vary by site type:

  • E-commerce: 3 to 5 pages per session (the user compares multiple products)
  • Media and blogs: 1.5 to 2.5 pages per session
  • SaaS with logged-in area: can exceed 8 to 10 pages per session

A low pages-per-session count may indicate:

  • An internal linking problem
  • Weakly engaging content
  • A high bounce rate

A very high count may reveal UX problems (the user is searching for information without finding it) or, conversely, very strong catalogue exploration.

This ratio is always used in combination with bounce rate and average time on page to build a complete picture of traffic quality.

Why it matters

For an e-commerce site, a user who views an average of 8 product pages per session is much closer to purchase than one who views 1.2. For an online media outlet, a high ratio means readers are following recommendations and extending their session.

It is also a key indicator for SEO and content teams: if blog pages generate fewer than 1.5 pages per session on average, internal linking deserves to be strengthened.

How to improve or use it

  1. 1Optimise your internal linking by adding relevant contextual links within your content.
  2. 2Embed recommendation blocks (related articles, similar products, popular content) at the end of your pages.
  3. 3Improve overall navigation with a clear menu structure and breadcrumbs.
  4. 4Create content series or thematic journeys that naturally encourage users to move to the next page.
  5. 5Reduce load times so they don't slow down navigation between pages.

With Sublim

Sublim displays pages per session in your main dashboard and lets you segment this indicator by traffic source, device and country, with no advanced configuration. All this data is collected without cookies, in full GDPR compliance, ensuring completeness unaffected by consent refusals.

Frequently asked questions

What is a good number of pages per session?

The norm varies by site type: e-commerce sites often reach 3-5 pages per session, media and blogs 1.5-2.5, and SaaS with logged-in areas can exceed 8-10 pages per session. What matters most is tracking the trend over time and comparing across traffic segments.

Is a low number of pages per session always a problem?

No. For a conversion-focused landing page, a user who reads the page and submits a form without navigating elsewhere may be exactly the desired outcome. For a blog, a reader who reads an in-depth article and leaves may have had an excellent experience. You should always contextualise with the page's goal and the conversion rate.

How are pages per session affected by Single Page Applications?

In an SPA, if virtual navigations are not properly tracked as pageviews, the pages-per-session ratio will be abnormally low (often close to 1). You need to implement virtual navigation tracking (via the History API) so that each route change is counted as a pageview.

Related terms

Pages per session: definition and interpretation, Sublim | Sublim Analytics