Skip to content

Insights / The practical edit

How to improve website speed without chasing a perfect score

Find what makes your website slow, prioritise useful fixes and understand Core Web Vitals without treating a performance score as the whole customer experience.

Back to all insights
How to improve website speed without chasing a perfect score

Your homepage can score well in a test and still feel slow when someone opens the menu. It can also score poorly because of one oversized image that is straightforward to fix. Start by finding the delay a customer actually experiences.

Check representative pages

Run PageSpeed Insights on the homepage, a service page, an article and a page with a form or checkout. Look at both mobile and desktop results. Save the report before changing anything so you have a baseline.

Separate laboratory tests from field data. A lab run is useful for diagnosis under a particular set of conditions. Field data reflects real visits over time, where enough data is available. A single test run does not describe every customer’s connection or device.

Understand the three Core Web Vitals

Largest Contentful Paint (LCP) measures loading of the main visible content. Interaction to Next Paint (INP) measures responsiveness to interactions. Cumulative Layout Shift (CLS) measures unexpected movement. The good thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, assessed at the 75th percentile of visits. See Google’s Web Vitals documentation.

Use those measures to decide where to investigate. A slow main image, an unresponsive menu and a jumping paragraph are different problems; they need different fixes.

Start with images and third-party scripts

Serve an image close to the size it will be displayed, use appropriate compression and provide smaller versions for smaller screens. Reserve its space with dimensions. Lazy-load images further down the page, but avoid delaying the main image that visitors see first.

Next, list the chat widgets, advertising tags, maps, video embeds and tracking scripts. Ask who uses each one and what would break if it were removed or delayed. A script can be small to download but expensive to run.

Look at what happens after the page appears

Open the menu, change a product option and submit a form. If the page looks ready but these actions stall, investigate long JavaScript tasks and repeated rendering. Reducing a hero image will not solve a blocked interaction.

Check server response times and caching as well. Cache public content where appropriate, while keeping account pages, baskets and personal data out of shared caches. Make sure cache clearing is part of the publishing workflow.

Retest the whole journey

After a change, repeat the same tests and use the same pages. Check whether the form still works, whether analytics still records the intended action and whether images remain clear. Keep a short record of what changed and the observed effect.

Speed work is easier to maintain when the team has a budget for new assets and scripts. Agree what a new video or plugin must justify before it goes live. For a broader review, use our website audit checklist.

Share this perspective LinkedIn ↗ Facebook ↗ WhatsApp ↗

Have a project in mind?

Let’s talk it through

Ideas worth exploring

A little perspective.

All insights