Find the delay customers actually feel
A speed report can show dozens of warnings. Begin with the mobile page that receives search traffic or drives enquiries. Watch when the headline appears, when the page stops moving, when a visitor can tap the action, and whether a form opens the keyboard correctly.
Core Web Vitals—LCP, INP, and CLS—are useful signals, but a good score cannot rescue a confusing offer or broken form. Use performance to protect a task, not to win a screenshot.
Fix the large, obvious assets
Images are often the biggest controllable cost. Export the right dimensions, use modern formats where supported, avoid loading below-the-fold images immediately, and keep the first screen sharp without shipping a camera original.
Fonts also matter. Use a small family and weight set, preload only what the first screen needs, and choose a fallback that does not cause layout jumps.
Audit scripts and embeds
Chat widgets, heatmaps, ads, social feeds, video players, and multiple analytics tags can delay interaction and create privacy work. Keep only tools tied to a decision. Load non-essential scripts after the main content or on the pages that need them.
A developer should be able to name every script, owner, purpose, and failure mode. ‘It came with the theme’ is not a performance strategy.
- Remove unused libraries and effects
- Defer non-essential widgets
- Use one accountable analytics setup
- Check consent and privacy behaviour
Measure after the fix
Compare real-user data, not only a single lab run. Check low-end phones, different networks, the first visit, and repeat visits. Verify that form delivery, tracking, accessibility, and search crawling still work.
Performance is maintenance: set an image budget, review new embeds, and test important releases. Small improvements compound when the site is updated every week.