Content revised 20 October 2026.
Page speed work is most useful when it fixes a measured delay in the real customer journey. Establish a baseline, identify the cause and check that optimisation preserves the page’s functions.
Measure representative pages
Test more than the homepage. Include a service page, article and any form or checkout page that matters to the business. Record the device, connection assumptions and whether the browser has cached resources. A repeat visit on a fast office connection can hide a problem new mobile visitors experience.
Match the work to the delay
A large image, slow server response and long-running script are different problems. Inspect the loading sequence before selecting a fix. Deferring every script without checking dependencies can break a menu or form, while shrinking a logo may do little if a large hero image is the main bottleneck.
Choose a focused first batch
- Serve images at appropriate sizes and compression.
- Remove genuinely unused or duplicated assets.
- Review scripts that block rendering or interaction.
- Investigate slow backend work and appropriate caching.
Check experience as well as loading
Watch for content that shifts as images or fonts arrive and controls that respond late. Core Web Vitals cover aspects of loading, interaction and visual stability, but a single laboratory score is not the whole customer experience. Keep essential video and useful images while improving how they are delivered.
Retest the journey
Repeat comparable measurements after each meaningful change. Open the mobile menu, play the video and try form validation in a safe test environment. Keep a record of the effect. Faster delivery supports usability; a score or pass status doesn't guarantee a search position.
Official guidance: Google’s Core Web Vitals overview.