Analyze storefront pages
Pages groups normalized storefront paths so teams can compare product, collection, cart, checkout, and other page families without treating every URL variant as a separate product surface.
Start with page outcomes
Use traffic, entry and exit behavior, the bounce proxy, and funnel progression to find pages where the journey appears to weaken. A high exit rate is context, not automatically a defect: an order confirmation page and a product page have different expected outcomes.
Open a page group
A page detail combines:
- visits, landings and bounce
- where shoppers came from (the previous page) and where they went next, including leaving the store
- exit share, friction share and order value per session
- issues observed on the page
- rage-click, dead-click candidate, repeated-submit, form-exit, and navigation-loop signals
- LCP, INP, and CLS distributions
- affected anonymous sessions
Issues on the page are drawn as bars against the page’s other issues. Environment segments and acquisition channels are drawn on a shared scale with the page group’s own value marked, so a segment that does worse than this page’s baseline, not the store’s, stands out. Use relative lift only when a comparable baseline exists.
Move into Issues for a grouped failure or Performance for a Core Web Vital investigation.