Reading the Page Details Report
How to read a single page's Analyze results, including the previous and next page paths, and how to reach pages missing from the list.
The page details report is where most real answers come from. Open the Insights tab, then Pages, then choose a page.
What the Report Shows
- Total sessions. Visits that included this page.
- Unique visitors. Individual people who saw it.
- Bounce rate. Sessions that started on this page and ended without a click or a second page.
- Average time on page. How long a typical visitor stayed.
- Traffic by device type. The desktop, tablet, and mobile split for this page specifically, which can differ sharply from the site average.
- Top events. The most clicked elements on the page, including calls to action.
- Top audiences. Traffic sources and top referrers for this page.
- Previous and next pages. The 10 internal pages visitors most often came from and went to.
Previous and Next Pages
These two lists are the most underused part of Analyze. They show the internal pages visitors viewed immediately before and immediately after this one, within the same session. A page counts each time it fully loads.
Read them as a path. If the next page list is dominated by the site search or the homepage, visitors are not finding their next step on the page and are backing out to look for it. If it is dominated by the page you hoped they would reach, the page is doing its job.
Pages Missing From the List
The Pages list holds up to 150 of the top site pages. CAS.org has far more pages than that, so most pages will not appear.
To see a page that is not listed, open the page in Webflow and click the View Analyze Mode icon in the top bar. That gives page-level data for any page. See Using Analyze Mode: Clickmaps, Fold, and Scroll Depth.
Reading a Page Well
- Compare the device split to the design. A page with mostly mobile traffic and a desktop-first layout has a fixable problem.
- Check whether the top events are the intended actions. If the most clicked element is a navigation link rather than the call to action, the page is being used as a waypoint.
- Use bounce rate in context. A high bounce on a page that answers one question completely may be fine.
- Confirm before concluding. One week of low traffic on a page proves very little. See Common Analyze Mistakes and Data Traps.