Core Web Vitals for Bloggers: What LCP, CLS, and INP Actually Mean
Core Web Vitals are the three performance metrics Google officially uses in ranking — and they're also part of what AdSense reviewers look at when assessing site quality. Most bloggers have seen these numbers in Google Search Console without fully understanding what they mean or what causes them.
This is the plain-language version: what each metric actually measures, why it matters for your blog specifically, and what to do when your number is bad.
LCP — Largest Contentful Paint
LCP is the time until the biggest visible thing on screen has fully loaded. On most blogs, this is your featured image or your headline. Good is under 2.5 seconds. Poor is over 4 seconds.
The most common cause on blogs: A large JPEG or PNG banner image that hasn't been compressed or converted to WebP. An image that's 800KB where 80KB would do the same job visually will tank your LCP every time.
Other LCP causes
Slow server response time (TTFB) is the second most common cause. If your server takes over 600ms just to start sending the page, everything else waits for that. Cloudflare's free CDN solves this for most shared hosting setups. Render-blocking JavaScript in your <head> is the third — scripts that load before your content delays everything.
CLS — Cumulative Layout Shift
CLS measures how much the page jumps around as it loads. Good is under 0.1. Poor is over 0.25. When an image loads and pushes text down, or an ad appears and shifts content — that's layout shift.
The fix is almost always the same: Set width and height attributes on your images. When the browser knows the image dimensions before it loads, it reserves the space in the layout. Without those attributes, it has to reserve nothing and then shift everything when the image arrives.
INP — Interaction to Next Paint
INP replaced FID as a Core Web Vital in 2024. It measures how quickly your page responds when a user taps or clicks something. Good is under 200ms. Poor is over 500ms.
Most blogs score fine on INP unless they have heavy JavaScript running — lots of tracking scripts, complicated widgets, or large JavaScript frameworks. If your INP is poor, check what scripts are running on page load using Chrome DevTools Performance tab.
How to check your actual numbers
Google Search Console shows your Core Web Vitals from real user data. AuditRoot calls the PageSpeed Insights API directly and gives you both desktop and mobile scores from Google's own measurement system — the same data Google Search Console shows, but instantly for any URL.
The numbers in PageSpeed Insights are real field data from Chrome users visiting your site, not lab simulations. This matters because your hosting environment, your CDN setup, and your actual content affect the real numbers in ways a simulation can't capture.
What to fix first
If you're applying for AdSense, focus on LCP first — it's the most common cause of poor performance scores and the easiest to fix. Compress your images, enable Cloudflare if you haven't, and check that your theme isn't loading unused scripts. A 20-point improvement in your performance score is achievable in an afternoon.
Check your Core Web Vitals
AuditRoot shows your real LCP, CLS, INP, FCP, and TTFB from Google's API — desktop and mobile separately. Free.
Check my site's scores →