Core Web Vitals (LCP, INP, CLS): How to Speed Up Your Website
Core Web Vitals in practice: LCP, INP and CLS thresholds, how to measure them in Search Console and PageSpeed Insights, and how to fix them step by step.
ReadMy website is slow
Pages take seconds to load, PageSpeed is in the red and Search Console keeps flagging poor URLs? We’ll find what’s slowing the site down and fix it in the code, instead of piling on another caching plugin.
In short
Speeding up a WordPress site starts with measurement, not with yet another plugin. We look at field data in the Core Web Vitals report in Search Console and in PageSpeed Insights, track down the cause with Chrome DevTools and Query Monitor, then fix it at the source: a leaner theme and plugin set, images converted to WebP or AVIF, server caching and a CDN. OrbitBuilder is a small studio that designs, builds and maintains WordPress sites. After rebuilding our own site we reached a CLS of 0 and a desktop LCP of about 0.3 s, and we show the effect of every fix in before-and-after data.
Sound familiar?
The site takes ages to load on my phone
Usually an LCP over 2.5 s caused by a large image, a slider or a slow server. We check data from real visitors, not just a single test run.
PageSpeed Insights shows a red score
The lab score points the way, but Google assesses your site on field data from Chrome users. We analyse both for every page type.
Search Console flags “Poor” URLs
The Core Web Vitals report groups similar URLs, so one slow template can drag down hundreds of pages. We find the template responsible.
Content jumps around while the page loads
That’s CLS: images without dimensions, banners injected above the content or a font swap. A button that moves at the last moment means people tap the wrong thing.
Menus and buttons respond with a lag
A poor INP usually means too much JavaScript: page builder scripts, chat widgets, ad pixels. We use DevTools to see which tasks are blocking the browser.
The WordPress dashboard is slow too
That points to the server or the database: an old PHP version, no object cache, thousands of revisions or spam left behind by a hack.
Causes
Elementor, Divi and WPBakery add their own styles and scripts, and marketplace themes load features you never use.
A contact form, slider or gallery plugin loads its code everywhere, including pages that don’t use it.
Photos straight off the camera, no WebP or AVIF, no dimensions, and lazy loading applied to the very image that should load first.
Cheap shared hosting, an old PHP version and no page cache mean a long wait before the browser receives anything at all.
A Tag Manager container with a dozen tags, ad pixels, live chat, embedded YouTube videos and maps, all loading from the first second.
Thousands of revisions, expired transients, options autoloaded on every request and sometimes spam left by a hack. On our old site that meant 9,915 posts.
How we fix it
We collect field data from Search Console and PageSpeed Insights plus lab tests for every page type, and record the results so there’s something to compare against.
In Chrome DevTools we break LCP and INP down into their parts, and in Query Monitor we look for slow queries and heavy plugins. You get a prioritised list of causes.
A current PHP version, OPcache, page caching (such as LiteSpeed Cache), object caching where it makes sense, and a CDN such as Cloudflare.
Conversion to WebP or AVIF, correct sizes and srcset, dimensions in the markup, fetch priority for the LCP image and self-hosted fonts.
We remove unnecessary plugins, load code only where it’s needed, fix the theme templates and tidy up third-party scripts.
We re-run the measurements, start fix validation in Search Console and hand over a before-and-after report. Field data refreshes over 28 days.
A PageSpeed Insights score is only a starting point. The number at the top of the report comes from a single lab test on a simulated phone. When Google assesses your site, it uses field data: measurements from real Chrome users over the previous 28 days. So before we change anything, we collect both kinds of data for every page type: the homepage, a service page, a blog post and, for stores, category and product pages too.
| Metric | Good result | What usually breaks it on WordPress |
|---|---|---|
| LCP, time to show the main content | 2.5 s or less | a heavy hero image or slider, lazy loading on the LCP image, a slow server |
| INP, response to a click or tap | 200 ms or less | page builder scripts, chat widgets, ad pixels and an overloaded Tag Manager |
| CLS, layout shifts | 0.1 or less | images without dimensions, banners and ads injected above the content, font swaps |
| TTFB, server response | 0.8 s or less | no page cache, an old PHP version, overloaded hosting, a bloated database |
The first three are the Core Web Vitals, with thresholds taken from web.dev’s documentation. TTFB isn’t one of them, but a slow server response pushes up LCP on every page. Once we know which metric is lagging and on which template, we go after the cause. In Chrome DevTools we break LCP down into its parts, and in Query Monitor we look for slow database queries and plugins loading where nobody uses them.
We cover the theory behind all three metrics, and how to improve them, in our guide to Core Web Vitals and speeding up your website. This page is about what we do when you hand the job to us.
A caching plugin, such as LiteSpeed Cache on a LiteSpeed server or WP Rocket elsewhere, cuts server response time. It won’t shrink the hero image, remove the scripts a page builder loads on every page or stop the layout shifting. We regularly see sites running two or three optimisation plugins at once. They duplicate minification, break each other’s lazy loading and knock the layout out after every update.
We’re also wary of tricks that improve the test score rather than the site. Delaying all JavaScript until the visitor first interacts can lift a PageSpeed score noticeably. The first tap then triggers every script at once, so the mobile menu and consent banner respond late, and INP in the field data gets worse.
So we fix the causes at template level:
Stores come with traps of their own. In older themes the script that refreshes the mini-basket sends a request to the server on every page view, even when the basket is empty. Product filters generate heavy database queries, and product pages load the gallery, variations and reviews all at once. Each of these can be reined in without removing features customers rely on. After the changes we place a test order to make sure the basket and payments still work.
Sometimes the page builder itself is the bottleneck and small fixes won’t get you there. In that case we’ll tell you plainly that rewriting the busiest templates, or the whole site, will cost less in the long run; see our page on website redesign. Speed also tends to slip with every new plugin and heavy banner, which is why our WordPress maintenance includes a monthly Core Web Vitals check.
The previous version of our site had the usual WordPress problems all at once: Elementor, a long list of plugins, 24 of which turned out to be unnecessary, and a database clogged with spam after a hack. It held 9,915 auto-generated posts and 2,238 spam tags and categories. Rather than optimise what was there, we did three things:
Not every site needs such a deep change. Fixes to the server, images and plugins, taking a few days, are often enough. Speed is also built into every site we create as part of our website design and development service, with a target of 90+ in PageSpeed on mobile.
If your site is already fast but still doesn’t bring in enquiries, the problem lies elsewhere. We cover it on our page about what to do when your website isn’t generating leads. And if you want to know what’s slowing yours down, send us the URL and we’ll tell you where to start.
Engagement options
For a business with its own developer that needs a diagnosis and a plan.
For a WordPress site or WooCommerce store that needs to get faster without a rebuild.
For a page-builder site where the builder itself is the bottleneck.
What you get
FAQ
It depends on the cause. Tuning caching, PHP and images takes a few days, while rewriting page-builder templates takes longer. The number of page types matters too, as does whether it’s a WooCommerce store. After the audit you get a quote broken down into specific fixes and their expected impact.
No. The lab score varies between runs and isn’t what Google uses to assess your site. The goal is good Core Web Vitals in the field data, from your real visitors. On mobile we aim for 90+, but never at the cost of a working menu, forms and analytics.
Google recommends achieving good Core Web Vitals and says this aligns with what its core ranking systems seek to reward. Speed won’t make up for content that misses the mark, though. Its biggest effect usually shows in visitor behaviour: fewer people give up before the page loads, and more of them reach the form.
It depends on your server. On LiteSpeed hosting, LiteSpeed Cache works best; elsewhere, something like WP Rocket. What matters is running one optimisation plugin, not three at once. No plugin will fix a bloated theme or hero images weighing several megabytes each.
Lab tests show the change straight away. The Core Web Vitals report is based on data from the previous 28 days, so the full effect appears after about a month. Validating a fix in Search Console also takes 28 days.
It can, which is why we make changes on a staging copy first, after a full backup. After each change we test the menu, forms and consent banner, plus the basket and a test order in stores. If anything goes wrong, we roll back to the previous version.
Not always. First we measure server response time with caching switched on. If it’s still above 0.8 s, or the host won’t run a current PHP version, we recommend a move and can migrate the site for you. More often, though, the problem lies in the theme and plugins rather than the server.
Elementor adds its own styles and scripts, and complex layouts with many nested containers increase the amount of code on each page. Some of that can be improved in its performance settings. For large, busy sites a hand-coded template usually pays off more, which is what we did on orbitbuilder.pl.
Insights

Core Web Vitals in practice: LCP, INP and CLS thresholds, how to measure them in Search Console and PageSpeed Insights, and how to fix them step by step.
Read
A step-by-step SEO audit checklist: indexing, redirects, content, Core Web Vitals, structured data and AI search visibility, with tools and priorities.
ReadFree first look
Share your site address and a short description of the problem. We reply within one business day with a first diagnosis and next steps.
How we can help
Your website
Google & AI
We use essential cookies and, with your consent, analytics (Google Analytics, Hotjar) and marketing cookies to understand how you use the site and improve it. Details in our privacy policy.