Tips to improve your website's loading speed
- Published
- Reading time
- 4 min
- Published by
- Konstantin

- LCP: time until the page's largest content has loaded
- ≤ 2.5 s
- INP: time from click or tap to visible response (200 ms)
- ≤ 0.2 s
- CLS: how much the content jumps while the page loads
- ≤ 0.1
Fast is not a feeling – it can be measured
Google measures perceived speed with three metrics, the Core Web Vitals. Here are the thresholds that apply today and the fixes that usually have the biggest effect.
A fast website gives a better experience, more visitors who stay and more who get in touch or buy. A slow page costs both business and trust – and it affects how Google assesses the page.
The good news is that speed can be measured and most problems can be fixed.
How Google measures speed: Core Web Vitals
Core Web Vitals are three metrics that describe how fast, responsive and stable a page feels:
- LCP (Largest Contentful Paint) – how long it takes before the page’s largest visible element, often an image or heading, has loaded. Good: 2.5 seconds or less. Poor: over 4 seconds.
- INP (Interaction to Next Paint) – how quickly the page responds visually when the visitor clicks, taps or types. Good: 200 milliseconds or less. Poor: over 500 milliseconds.
- CLS (Cumulative Layout Shift) – how much the content moves while the page loads. Good: 0.1 or less. Poor: over 0.25.
INP replaced the previous metric FID (First Input Delay) on 12 March 2024. FID only measured the delay of the first interaction. INP looks at every interaction during the visit and is therefore a stricter measure.
A page passes Core Web Vitals when all three values are good for at least 75 percent of page views, measured separately on mobile and desktop. In other words, it is real visitors’ experience that counts – not a single test on a fast computer.
How does the web measure up?
The share of websites that pass Core Web Vitals has grown, but on mobile more than half still do not.
| Desktop | Mobile | |
|---|---|---|
| 2021 | 41% | 32% |
| 2022 | 44% | 31% |
| 2023 | 48% | 36% |
| 2024 | 55% | 44% |
| 2025 | 56% | 48% |
Source: HTTP Archive, Web Almanac 2025 (Chrome UX Report)
It is LCP that most often trips up mobile pages. INP and CLS are passed by considerably more:
- LCP62%
- INP77%
- CLS81%
Source: HTTP Archive, Web Almanac 2025 (Chrome UX Report)
You can find your own starting point in the Core Web Vitals report in Google Search Console and in PageSpeed Insights, which shows both field data from real visitors and a lab test with concrete suggestions for improvement.
Improve LCP: images, server and cache
- Optimise the images. Use modern formats such as AVIF or WebP, compress them and deliver the right size for each screen with
srcset. - Prioritise the main image. The largest image above the fold should not be lazy-loaded. Give it high priority so that the browser fetches it first.
- Speed up the server. A host with short response times makes a difference. Heavily loaded shared servers are a common bottleneck; a VPS or a managed platform gives more consistent performance.
- Use a CDN. A CDN delivers files from servers close to the visitor and reduces the load on your own server.
- Cache. Store finished pages and files so that the server does not have to rebuild them on every visit.
- Minimise redirects. Every redirect adds an extra round trip to the server before the page even starts loading.
Improve INP: less JavaScript
- Clean up third-party scripts. Chat widgets, tracking tags and ad scripts run in the same thread as your own interactions. Remove what is not used and load the rest after the page has become interactive.
- Fewer plugins. In WordPress and WooCommerce, each plugin often adds its own scripts and styles. Keep only the ones you need and keep them up to date.
- Break up long tasks. Heavy JavaScript that runs in one go blocks clicks and taps. Split up the work and defer what is not needed straight away.
- Minify and compress. Minify CSS and JavaScript and serve the files compressed.
Improve CLS: reserve space
- Set width and height on images and video, so that the browser knows how much space they take up before they have loaded.
- Reserve space for anything that loads late, such as ads, embeds and cookie banners. A consent banner that pushes the page down after loading is a common cause of poor CLS.
- Load fonts smartly. Use WOFF2, include only the characters and weights you need and preload the most important ones. Fewer fonts mean both faster loading and less jumping in the text.
Architecture: when optimisation is not enough
Sometimes the problem lies in the foundations: a theme with a lot of code, a CMS that builds every page on every visit or a platform that cannot be optimised any further.
Two architectural choices that help:
- Prefetching. The browser can fetch, or even prepare, the next page in advance when the visitor is likely to go there – for example the checkout once a product has been added to the cart.
- Headless or static pages. With a headless CMS, content management is separate from presentation, and pages can be built in advance and delivered via a CDN. Read more about headless solutions.
Would you like help finding out what makes your website slow? See how we work with technical SEO.
Key insights
- 01
INP has replaced FID
Since 12 March 2024, Google has measured responsiveness with INP, which counts every interaction during the visit – not just the first.
- 02
Measure with real visitors
The thresholds apply to the 75th percentile of real page views, separately for mobile and desktop. A good lab test is not enough.
- 03
LCP is hardest on mobile
Large images and a slow server are the most common causes. Start with the page's largest image and the response time.
- 04
Fewer scripts, better INP
Every third-party script and plugin has a cost. Remove what is not used and load the rest later.
















