In Search Console, under "Core Web Vitals", there is a red bar with 40 URLs, and nobody in the company knows what LCP, INP and CLS mean, let alone how to fix them. Yet the three values have been a ranking factor for years and, more importantly, a direct lever on enquiries and orders: a study by Google and Deloitte showed that a website 0.1 seconds faster increases retail conversion rates by up to 8 percent.
This guide explains the three metrics without jargon, shows where the real numbers are, and lists per metric the measures that make the biggest difference in our projects, for WordPress, shops and modern JavaScript websites.
Red values and no time? We measure your website, find the three biggest brakes and fix them at a fixed price. Have your Core Web Vitals checked →
The three metrics and their thresholds
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Time until the largest visible element is loaded, usually the hero image or main heading | up to 2.5 s | 2.5–4 s | over 4 s |
| INP (Interaction to Next Paint) | How quickly the page responds to clicks, taps and keyboard input, measured across the whole visit | up to 200 ms | 200–500 ms | over 500 ms |
| CLS (Cumulative Layout Shift) | How much content jumps while loading, for example when an image or banner claims space late | up to 0.1 | 0.1–0.25 | over 0.25 |
Where to find the real numbers
| Tool | Data type | Use |
|---|---|---|
| Google Search Console, Core Web Vitals report | Field data from real Chrome users, grouped by similar URLs | The benchmark Google uses. This is where it has to turn green |
| PageSpeed Insights | Field data per URL plus lab measurement with diagnostics | Root cause analysis for a single page |
| Chrome DevTools, Performance tab | Lab data live in the browser | Finding individual long tasks and layout shifts |
| Own measurement with the web-vitals library | Field data from all visitors, even without Chrome opt-in | For websites with little traffic that have no data in Search Console |
Improving LCP: show the largest element faster
On SME websites LCP is almost always the hero image or a slider. The most effective measures, in this order:
- Lower server response time. Without cache and with old PHP, 800 milliseconds pass before the browser even starts. How to solve that in WordPress is in our article WordPress slow.
- Optimise the hero image. WebP or AVIF, no larger than the display area, under 200 kilobytes. A 2 megabyte photo as the opening image is the most common LCP killer.
- Prioritise the hero image, do not defer it. No lazy loading for the first visible image, instead
fetchpriority="high"and a preload in the head:
<link rel="preload" as="image" href="/images/hero.webp" fetchpriority="high">
<img src="/images/hero.webp" width="1200" height="600" fetchpriority="high" alt="…">
- Reduce render-blocking CSS and JavaScript. Critical CSS inline, the rest loaded later; scripts with
defer, remove page builder bloat. - Host fonts locally and load them with
font-display: swap, the most important font via preload. - Replace the slider. A slider with five images loads five images and a JavaScript bundle before the first appears. A static image with a clear message is faster and usually converts better.
- CDN and compression. Brotli, HTTP/2 or HTTP/3, images from the CDN.
- Render server-side. On React or Vue websites the content must be in the HTML, not created only after the JavaScript runs.
Improving INP: the page should respond instantly
INP replaced the old FID value in 2024 and is stricter: it measures every interaction during the visit, not just the first. Poor INP values almost always come from too much JavaScript on the main thread.
- Reduce the amount of JavaScript. Page builders, sliders, animation libraries, chat widgets and tracking often load over a megabyte of scripts. Every kilobyte not loaded does not have to be executed.
- Defer third parties. Load tracking, chat and maps only after consent or after the first interaction. That improves INP and privacy at the same time.
- Break up long tasks. Scripts that run longer than 50 milliseconds in one go block every input. In DevTools they are marked red.
- Keep event handlers lean. Do only what is necessary on click, defer heavy work or move it to a web worker.
- Reduce hydration. With React and Next.js make only the components interactive that need it; the rest stays static HTML.
- No layout calculations in handlers. Reading and writing sizes in a loop forces the browser into constant recalculation.
Fixing CLS: nothing may jump
CLS is the easiest metric to solve because the causes are visible:
- Images and videos with dimensions.
widthandheightin the tag oraspect-ratioin CSS, so space is reserved before the file loads. - Reserve space for dynamic content. Cookie banners, notice bars, embedded maps and ad slots get a fixed height or appear as an overlay that shifts nothing.
- Fonts without jumps. Web fonts with
font-display: swapand a fallback font with adjustedsize-adjust, so text does not reflow on swap. - Do not insert content above existing content. Banners that appear at the top later push the whole page down.
- Animate with
transforminstead oftoporheight. Only then do they stay free of layout shifts.
Typical problems by platform
| Platform | Typical problem | Fix |
|---|---|---|
| WordPress with Elementor or Divi | Large CSS and JavaScript bundles, sliders, INP over 300 ms | Disable modules, caching with JavaScript delay, replace slider with a static image |
| WooCommerce | Cart fragments request on every page, many product images, CLS from price display | Limit cart fragments to shop pages, set image dimensions, placeholders for prices |
| Shopify | Theme apps load dozens of scripts, LCP from large hero images | Clean out apps, compress images in the theme, defer app scripts |
| React or Vue as a single-page app | Empty HTML, LCP only after JavaScript, hydration blocks INP | Server-side rendering or static generation with Next.js or Nuxt, partial hydration |
| Builders such as Wix or Squarespace | Little influence on the technology | Optimise images, reduce fonts, minimise third parties; consider a platform change if values stay red |
| Static website | Usually good, problems from fonts and third parties | Fonts local, defer tracking |
The order that brings the most
By the 80/20 principle, four measures solve most red values:
- Server response time through cache and current PHP or hosting
- Hero image optimised, prioritised, with dimensions
- Fonts local with swap and preload
- Third-party scripts deferred or removed
Free initial assessment: Send us your address. We read field and lab data and tell you which three measures have the biggest effect for you. Send your address →
What Core Web Vitals mean for your business
Google calls Core Web Vitals one ranking factor among many, and with equivalent content it tips the balance. More important is the direct effect: visitors who stare at a white screen on their phone for three seconds go back to the search and click the next provider. Every second of LCP measurably costs enquiries, every layout jump costs trust, every sluggish response costs orders. What good values cost: an audit with a list of measures is CHF 300 to 600, implementation depending on platform between CHF 500 and 3,000. For websites we build, green values are part of acceptance.
Frequently asked questions
How important are Core Web Vitals for ranking?
One factor among many that can tip the balance with similar content. The bigger effect is conversion: fast pages bring more enquiries from the same visitors.
Why does PageSpeed Insights show green but Search Console red?
PageSpeed measures in the lab with a simulated device, Search Console with real visitors. Your visitors evidently have slower devices or networks. Search Console is what counts.
How long until Search Console turns green?
Field data covers 28 days. After an improvement it therefore takes up to four weeks for the report to flip.
Does my cookie banner cause CLS?
If it pushes content down, yes. As an overlay or with reserved space it causes no layout shift.
Mobile or desktop, which counts?
Both are rated separately, but mobile is usually worse and for most SMEs the larger share of visitors. Optimise for mobile first.
Conclusion: three numbers, four measures, measurably more enquiries
Core Web Vitals are not rocket science: LCP depends on the server and the hero image, INP on JavaScript, CLS on missing dimensions. Implement the four most important measures and check with the field data in Search Console, and most SME websites are green within a few weeks, and you will see it in your enquiries.
We optimise Core Web Vitals for Swiss SMEs at a fixed price, monitor them continuously in the maintenance package and make sure with search engine optimisation that the fast site is also found.
Want your website green on all three values? Send us the address and we will come back with measurements and a plan. Get in touch →
Further reading
core web vitals, lcp, inp, cls, pagespeed, performance, seo, website help


