Core Web Vitals judge a page at the 75th percentile of real Chrome user visits over 28 days, which means the lab score you see once in PageSpeed Insights is only part of the picture.
Three metrics make up the set: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability. INP replaced First Input Delay in March 2024. This guide gives you the thresholds, the tools to read your real data, and a fix list that suits the typical blog: big hero images, ad and embed slots, many plugins and third-party scripts.
The Three Metrics and Their Thresholds
| Metric | Measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP | How fast the main content loads | 2.5 s or less | 2.5 to 4 s | Over 4 s |
| INP | How quickly the page responds to clicks and taps | Under 200 ms | 200 to 500 ms | Over 500 ms |
| CLS | How much the layout jumps while loading | Under 0.1 | 0.1 to 0.25 | Over 0.25 |
A page passes only if all three metrics are in the good range at the 75th percentile of real visits. One red metric is enough to fail. Treat Core Web Vitals as a user-experience signal that sits alongside content relevance; a fast page with weak content will not outrank a helpful one, but a very slow page can lose visitors before they read a word.
How to Measure Your Blog Properly
- Search Console, Core Web Vitals report: groups URLs by status using real-user data, so you can fix whole templates at once.
- PageSpeed Insights: shows field data from the Chrome User Experience Report when available, plus lab diagnostics to explain the causes.
- Chrome DevTools: use the Performance panel to find long tasks and layout shifts on a test run.
- web.dev guidance: reference documentation for each metric and its fixes.
Remember the difference between lab and field data. Lab tools simulate a visit and are good for debugging. Field data reflects real devices and networks, which is what counts for the report. Because the field window is 28 days, wait a few weeks after a fix before judging the result.
Fixing LCP on a Blog
On most blogs the LCP element is the featured image or the headline block. The goal is to deliver it quickly and early.
- Preload the hero image and do not lazy-load it; lazy loading belongs to images below the fold.
- Use modern formats and right sizes: WebP or AVIF, with responsive srcset so phones do not download desktop-size files.
- Reduce render-blocking CSS and JavaScript: defer what is not needed for the first view.
- Improve server response: good hosting, page caching and a CDN lower the time before anything can load.
- Trim fonts: limit weights and preload only the font used above the fold.
Fixing INP and CLS
Improving INP
INP is affected by main-thread work. Heavy scripts block the browser from reacting to a tap. Audit third-party scripts (ads, chat widgets, analytics tags, social embeds), remove the ones that do not earn their place, and load the rest after interaction or on demand. Split long tasks and avoid large plugins that run code on every click. Test menus, search boxes, accordions and comment forms, since these are the typical interactions.
Improving CLS
- Set width and height (or aspect-ratio) on every image and video so space is reserved.
- Reserve space for ads, banners and embeds with fixed containers.
- Use font-display: swap and fallback fonts with similar metrics to reduce text jumping.
- Avoid inserting content above existing content after load, such as cookie bars that push the page down.
A Simple Order of Work
Start with the template-level issues that affect every post: the hero image, fonts, theme scripts and ad slots. Fix the worst metric first, retest in PageSpeed Insights, and then wait for the Search Console report to catch up.
