11 Oct 2026 · 4 min read · Lunor Medya · Updated 21 Nov 2026
How to Improve Website Speed and Core Web Vitals: Steps for LCP, INP and CLS
Practical steps to improve LCP, INP and CLS, from finding the failing metric and template to fixes for the server, images, JavaScript and layout.
“The site is slow” does not tell you where to start. Speed work begins by finding which metric fails on which page type and on which device; otherwise time goes into polishing areas that are already fine. This article sets out practical steps to improve Core Web Vitals, metric by metric. For definitions and thresholds see our article on what Core Web Vitals are; in short, the targets are 2.5 seconds or less for LCP, 200 milliseconds or less for INP and 0.1 or less for CLS.
1. Diagnosis: where is the problem?
- Open the Core Web Vitals report in Search Console for mobile and desktop separately, and note which metric fails in which group of pages.
- Test a sample URL from the group in PageSpeed Insights. Field data shows the situation; the lab section's suggestions point to causes.
- Reproduce the problem in the Chrome DevTools Performance panel with network and CPU throttling.
A fix to a template applies to every page using it, so plan the work by template rather than URL by URL.
2. Improving LCP
Speed up server response
- Use page caching; pages rebuilt from the database on every visit delay the first byte.
- Choose a server or content delivery network close to your visitors.
- If you hit resource limits on shared hosting, review your infrastructure.
Bring the LCP element forward
- Do not lazy-load the main above-the-fold image.
- Give that image high priority (the fetchpriority attribute) or preload it.
- Serve it at its displayed size in a modern format such as WebP or AVIF.
- If the LCP element is a CSS background or an image injected by JavaScript, move it into markup the browser can discover early in the HTML.
Reduce render-blocking resources
- Defer CSS and JavaScript not needed for the first screen.
- Load only the font weights you use, and consider self-hosting fonts.
3. Improving INP
Most INP problems come from JavaScript that keeps the main thread busy for long stretches.
- Inventory third-party scripts: live chat, heatmaps, multiple analytics and ad tags, social embeds. Remove what is not really used and load the rest after interaction where possible.
- Break up long tasks: Split heavy work triggered by a click into chunks so the browser gets a chance to update the screen.
- Give visual feedback first: Show a loading state as soon as a button is pressed, then do the heavy work.
- Shrink the DOM: Menus with thousands of elements and the nested layers of page builders slow every update.
4. Improving CLS
- Give every image and video width and height values, or define the aspect ratio in CSS.
- Reserve space in advance for ad slots, announcement bars and embeds.
- Show the cookie notice as an overlay that does not push content down.
- Reduce the size difference between the web font and its fallback; when text metrics change, paragraphs shift.
- Do not insert new elements above existing content without a user interaction.
5. Notes for WordPress sites
- Look less at the number of plugins and more at what each loads on every page; a form script needed only on the contact page may be loading site-wide.
- Heavy page builders and multipurpose themes usually produce a large DOM and excess CSS.
- Caching and image optimisation plugins help, but their settings need testing; a misconfigured combine option can break pages.
To turn updates and plugin clean-up into a regular habit, see our article on a WordPress maintenance routine.
6. Validation and follow-up
- Confirm the change in a lab test first.
- Start validation for the issue in Search Console. Because field data is collected over a 28-day window, the result takes a few weeks to settle.
- Measure again after every new script or plugin; speed is not something you win once and forget.
If the server is the bottleneck, have a look at our hosting and infrastructure options. To hand off speed improvements and follow-up, see our technical SEO service, or the website maintenance and support package for regular checks.