Performance work should begin with real user paths, not a single laboratory score. Identify the pages that attract search traffic or generate enquiries, then measure their largest content, interaction delay, and layout stability on representative devices.
Large hero images, unoptimised screenshots, custom fonts, consent tools, analytics, and embedded services are common causes of slow first views. Correct sizing, modern formats, priority loading, font discipline, and a smaller script budget often produce the largest gains.
INP improves when long JavaScript tasks are broken up and unnecessary client-side work is removed. CLS improves when images, banners, cards, and dynamic content have stable dimensions before they load.
The goal is a fast commercial experience, not a perfect score in isolation. Measure after deployment, monitor regressions, and include performance in the content and release process.
For LCP, inspect the actual largest element on each template. A hero image may need responsive source sizes, a preload, stronger compression, or simply smaller dimensions. If the largest element is text, font delivery and render-blocking CSS may be the real issue. Fix the observed element instead of applying a generic optimisation checklist.
For INP, record interactions that feel slow: menu opening, filters, carousels, form validation, and consent controls. Reduce hydration work, defer nonessential scripts, split long tasks, and avoid attaching expensive handlers to every card. The page should remain usable while analytics and decorative behaviour load later.
CLS is usually preventable with explicit image dimensions, stable font metrics, reserved banner space, and predictable injected content. Test real states such as validation errors, cookie notices, slow images, and long translations. A layout that is stable only on a fast developer machine is not stable enough.
Create a performance budget for images, JavaScript, fonts, and third-party tools, then test it in the release workflow. Combine lab diagnostics with field data from Search Console or a real-user monitoring tool. Review templates individually because a fast homepage can hide a slow article, product, or campaign page.