Core Web Vitals 2026 – LCP, INP, CLS without the bullshit

Core Web Vitals is 3 Metrics Google Uses to Measure User Experience —and which influence search engine rankings. Good values mean better rankings, lower bounce rates, and higher conversions. I'll show you exactly what they measure, how to check them, and how to improve them in WordPress.

In short

• 3 indicators: LCP (loading speed), INP (interaction responsiveness), CLS (visual stability).
• Google Goals:
• LCP < 2.5 s
• INP < 200 ms
• CLS < 0.1
• The 75th percentile is measured — 75% of visits must be within the goals.
• INP replaced FID in March 2024 - stricter metrics, more pages "break".

What is Page Experience?

Google officially uses CWV as of 2021 ranking factor. A page with good CWV and a page with bad CWV, all else being equal, will get a higher ranking.

Weight in the ranking: about 5–10% of the entire algorithm. A lot? A little? Enough to decide who will be in the TOP 5 and who in the TOP 15.

LCP – Largest Contentful Paint

What is this

LCP measures how long it takes to load the main element on a page. Typically this is an "above the fold" image or a large heading.

When a user enters your website:
– 0 ms – clicked
– 200 ms — server responds (TTFB)
– 800 ms - first CSS/HTML loads
– 1,200 ms — fonts loaded, text visible
– 1,800 ms - large photo loads = LCP

Goals

• Good: < 2.5 sec
• Needs improvement: 2.5–4.0 sec
• Weak: > 4.0 sec

How to improve

1. Optimize LCP element (usually the hero of the picture):
2. WebP/AVIF instead of JPG (50% less weight)
3. width i height w atrybutach (Google preloaduje)
4. fetchpriority="high" w <img>

5. No lazy load for LCP image (lazy load ONLY for images below fold-a)

6. Shorten TTFB (Time to First Byte):

7. Better hosting (NVMe, LiteSpeed)
8. PHP Cache (OPcache)

9. CDN (Cloudflare, BunnyCDN)

10. Eliminate blocking resources:

11. Critical Inline CSS
12. Async/defer for non-critical JS
13. Preload key fonts

INP – Interaction to Next Paint

What is this

Latest metrics (from March 2024), replaced FID. It measures page response delay for every user interaction (click, tap, keyboard).

INP = worst interaction during the session (98th percentile to be precise). If you click on the menu and wait 350 ms, that's your INP.

Goals

• Good: < 200 ms
• Needs improvement: 200–500 ms
• Weak: > 500 ms

What Breaks INP in WordPress

1. Heavy JavaScript — Elementor Pro with motion effects, sliders, popup managers
2. No code splitting — the entire page JS loads for 1 function
3. Blocking third-party - Google Tag Manager, livechat, Hotjar, Facebook Pixel
4. Too many event listeners — JavaScript that executes 10 functions on every click

How to improve

1. Defer / async for all non-critical JS
2. Lazy-load third-party — Hotjar, load livechat only after the first interaction
3. Turn off motion effects Elementor Pro (leave single animations)
4. Remove unnecessary plugins loading JS site-wide
5. Web Workers for heavy calculations (rarely used in typical WP)

In practice, 80% of INP problems in WP are solved WP Rocket + Perfmatters + Light Theme.

CLS – Cumulative Layout Shift

What is this

CLS measures how much a page "jumps" while loading. You enter, read the headline, click - and suddenly an ad loads, the content jumps, you click the wrong link.

CLS = sum of all layer jumps, weighted by their size.

Goals

• Good: < 0,1
• Needs improvement: 0,1–0,25
• Weak: > 0,25

What spoils the CLS

1. Obrazy bez width/height — the browser doesn't know how much space to reserve
2. Adsense ads — variable banner height
3. Embed YouTube / Twitter — iframe loads asynchronously
4. Dynamic content injected after load — popups, cookie banners
5. Web fonts bez font-display: swap — fallback font is smaller/larger, text jumps

How to improve

1. width i height on every image and iframe
2. Reserved space dla reklam (kontener z min-height)
3. Cookie banner at the bottom, not the top (less noticeable jump)
4. font-display: swap + matched fallback fonts — inherited font metrics
5. Ratio aspect in CSS:
   css .video-container { aspect-ratio: 16 / 9; }

How to measure CWV

1. PageSpeed Insights (public, free)

pagespeed.web.dev — enter URL, you will get results field data (real users from the last 28 days with Chrome) and lab data (simulation during test).

2. Search Console - Core Web Vitals

GSC → Experience → Core Web Vitals. Shows all pages of your website Divided into "Good," "Needs Improvement," and "Poor." Perfect dashboard for prioritization.

3. Chrome User Experience Report (CrUX)

Bigquery / public dataset — actual data from Chrome users. Only for sites with high traffic (several thousand uniques per day).

4. Web Vitals extension (Chrome)

A plugin that shows CWV in real time while surfing. Quick testing while editing.

5. Lighthouse in DevTools

F12 → Lighthouse → Generate Report → mobile mode → Core Web Vitals from "lab data" + suggestions.

6. Real User Monitoring (RUM)

For advanced users: Cloudflare Analytics, Datadog RUM, New Relic – show CWV per user, country, device.

Field data vs. Lab data - what does Google count?

Field data only. Lab data (simulation in PageSpeed) is indicative — Google ranks based on real users from Chrome.

Meaning:
– Your site in PageSpeed Insights “Lab” 95/100, but “Field” shows LCP 4.5 s — Google sees 4.5 seconds.
– No field data (small site) – Google uses lab data as fallback.

Frequently asked questions

“I have 95/100 in PageSpeed, but CLS = 0.3 – what?”

A score of 95/100 is a lighthouse score. CWV are separate. You can have a 95 overall score and still be "Poor" in CLS.

"Mobile vs Desktop - Which is More Important?"

Mobile. Google primarily uses mobile-first indexing. If mobile CWVs are bad, desktop won't help.

“How long does it take for Google to “notice” a fix?”

Field data updates from 28 days late (rolling window). After repair, please allow 4–8 weeks for real impact.

“Are CWVs more important than backlinks?”

NO. Links + content is still 70% of the ranking. CWV is a tie-breaker—the difference between 2nd and 3rd place, not between 30th and 3rd.

What's next

This week:

1. Come in pagespeed.web.dev and test the mobile home page
2. If any metric is red - select one for repair
3. Deploy the fix (typically 2-8 hours of work)
4. Return to GSC after 28 days and see if your field data has improved.

We provide Core Web Vitals optimization as a separate service — package from PLN 1,500, guaranteed result "Good" in all 3 metrics. Order an audit.