Begin with a user journey
Aggregate scores can hide the page, query, or dependency that actually prevents a customer from completing important work.
Measure both sides of the boundary
Browser timing, server traces, database behavior, and third-party latency should be evaluated together under repeatable conditions.
Prioritize by business impact
The final output should rank changes by expected impact, implementation effort, and risk rather than presenting an unfiltered list of observations.