Is your site quietly killing conversions?
Fix it fast with our 150-Point CRO Checklist:
• Find out what’s broken
• Learn how to fix it (and turn clicks into cash)
• Use the same tactics that drove $4B+ in ecommerce revenue
Pages Per Session
Short description
Pages per session is the average number of pages viewed during a single visit. It indicates browsing depth and the ease or difficulty of finding products. The goal is the right number of pages that lead to confident purchases.
Why it matters
This metric can signal both healthy exploration and harmful friction. If pages per session rise along with conversion, your catalog and navigation likely support discovery. If pages rise while conversion falls, shoppers may be struggling to find what they want. Pages per session is a useful early signal during navigation or filter redesigns. It also helps quantify the impact of on-site recommendations and content hubs.
How it works
Calculate pages per session by dividing total pageviews by total sessions. Segment by device, channel, and landing page to see differences. Single-page sessions lower the average, so review distribution, not only the mean. Combine this metric with time on site and funnel progression to avoid false positives. Monitor internal search usage and PDP view to add-to-cart as companion signals.
Example in ecommerce
An outdoor brand upgrades category filters, adds quick add, and improves sort options. Pages per session increase on mobile, and add-to-cart rises because shoppers find relevant items faster. The team monitors the PDP view to add-to-cart ratio to confirm quality, not only quantity. The same template rolls out across similar categories with consistent gains.
Common mix-ups
Pages per session is not pageviews. It normalizes pageviews by visit count to show depth. It is not a satisfaction score by itself either. Some high-intent sessions have very few pages because the path to purchase is clear, for example a returning customer buying a replenishment.
Best practices
- Improve category filters and search to help visitors find products quickly.
- Use related products and editorial content to guide exploration.
- Add quick add and size selectors on listing pages to reduce extra steps.
- Track PDP view to add-to-cart ratio as a quality check.
- Compare depth across landing types to prioritize template work.
Industry benchmarks
- Large catalogs tend to produce higher pages per session than focused shops.
- Mobile depth is typically lower than desktop due to screen size and attention spans.
- Use your highest-converting journeys to set depth targets for similar flows.
Related terms
You made it all the way down here?
Might as well give us a shot, right? It'll change the way you approach CRO. We promise. In fact, our friend Nate over at Original Grain used element-level revenue data from heatmap to identify high-impact areas of his website to test, resulting in a 17% lift in Revenue per Session while scaling site traffic by 43%. Be like Nate. Try heatmap today.
