Performance work should improve the experience real visitors receive, then prove the change in the templates and field data that matter.
We segment CrUX, Search Console and real-user monitoring where available to find affected origins, routes, devices and templates. Lab testing then reproduces the conditions behind the field pattern instead of replacing it with one perfect test run.
Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift each require different evidence. We inspect server latency, render paths, resource priority, main-thread work, component behaviour and layout allocation.
We define changes at the code, asset or delivery layer, test representative templates and compare before and after traces. Field metrics are monitored after release because user data needs time to reflect the new experience.
We move from diagnosis to implementation with clear priorities, owners and checks at each stage.
Collect the technical, search and commercial evidence behind the problem.
Choose the work by impact, confidence, effort, dependency and risk.
Support the people changing templates, content, platforms and processes.
Test the release, monitor search processing and use the results to guide the next decision.