A two-week frontend performance audit cannot cover every template. We ask stakeholders to score candidates on three axes: revenue or retention impact, share of mobile sessions, and how many other pages reuse the same layout shell.
Journeys that score high on all three become the core five. A beautiful but low-traffic microsite usually waits. An authenticated settings page that shares the shell with checkout may ride along as a sixth “shell-only” check without expanding full journey instrumentation.
Document the cuts in the kickoff note. Mid-audit scope creep is the fastest way to turn a ranked backlog into an unfinished encyclopedia. If a festival campaign needs a seventh path, we issue a change note rather than silently diluting depth.