Core Web Vitals are three measurements Google takes from real visitors to your pages: how fast the main content shows up, how quickly the page reacts when someone taps or clicks, and how much the layout jumps around while loading. If your site feels slow, one of those three is usually the reason.
For a small blog, most of the problem tends to come from a short list of things: oversized images, too many fonts, third-party scripts and ads, and content that loads without space reserved for it. Most of that is fixable without writing code. Measure first, then work down the list below in order.
The three metrics and the numbers to aim for
| Metric | What it measures | "Good" |
|---|---|---|
| LCP (Largest Contentful Paint) | Time until the biggest thing on screen appears, usually the top image or headline | 2.5 seconds or less |
| INP (Interaction to Next Paint) | Delay between a tap or click and the page visibly responding | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much content moves unexpectedly while loading | 0.1 or less |
Google judges each one at the 75th percentile of real visits, which means three out of four visits need to hit the "good" number. Phones and desktops are assessed separately, and phones are almost always the harder test.
If you've read older guides that talk about FID (First Input Delay), ignore that part. INP replaced FID as a Core Web Vital in March 2024.
How much do Core Web Vitals affect rankings?
Less than most speed-tool marketing suggests. Google's page experience documentation says Core Web Vitals are used by its ranking systems, and in the same breath says good results in these reports don't guarantee your pages will rank at the top. It also says Search tries to show the most relevant content even when the page experience is sub-par.
So a fast page with a thin answer won't outrank a slower page with a better one. Speed can help when several pages answer the query about equally well. I'd treat it as a reader-experience job first: people leave pages that load slowly or jump under their thumb, whatever the rankings say.
How to check your Core Web Vitals
Two free tools cover it.
PageSpeed Insights (pagespeed.web.dev). Paste in a URL and you get two different kinds of result on one page, which is where most confusion starts:
- Field data, at the top. This comes from real Chrome users over the previous 28 days, and it's what the Core Web Vitals assessment is based on.
- Lab data, underneath, with the 0β100 performance score. This is one simulated page load. It's useful for finding causes, and it updates the moment you change something.
The two often disagree, because one is a single test under fixed conditions and the other is real visits on every kind of phone and connection. When they conflict, trust the field data. A lab test also can't measure INP, because nobody is tapping on a simulated page.
Small sites often see no field data at all. If a page doesn't get enough Chrome traffic, PageSpeed Insights falls back to data for your whole site, and if there isn't enough of that either, you only get the lab test. That's normal for a new blog. Use the lab results to find problems and check again as traffic grows.
Search Console's Core Web Vitals report uses the same real-user data across your whole site. It sorts URLs into Good, Need improvement and Poor for mobile and desktop, and groups similar pages together, so a template problem shows up as one issue affecting many URLs. It's the better tool for deciding which type of page to fix first. If you haven't set up Search Console yet, that's step one of a one-hour SEO audit.
Test a typical article page as well as your homepage. Articles are where search visitors land.
Symptom, likely cause, fix
| What you see | Likely cause | Fix |
|---|---|---|
| Slow LCP | Huge or lazy-loaded top image | Resize, compress, load it first |
| Slow LCP on every page | Slow server response | Caching, CDN, better hosting |
| Poor INP | Too much JavaScript: ads, widgets, plugins | Remove or delay scripts |
| High CLS | Images, ads or embeds with no reserved space | Set dimensions, reserve slots |
| Text flickers or jumps | Web fonts loading late | Fewer fonts, self-host them |
Fix images first
Images are the biggest payoff on most blogs, because the LCP element is so often the featured image at the top of the post. Five habits cover it:
- Resize before you upload. A photo straight from a phone or a stock site can be 4,000 pixels wide. Your content column is probably under 800. Export at roughly the largest size it will display (up to double for sharp screens).
- Use a modern format. WebP or AVIF files are much smaller than the JPEG or PNG equivalent at similar quality. Many platforms and image plugins convert on upload.
- Give every image a width and height. With those two attributes in place, the browser reserves the right amount of space before the image arrives and nothing below it jumps. Most editors add them automatically; older themes and hand-pasted HTML often don't.
- Lazy-load images further down the page. Lazy-loading means an image isn't downloaded until the reader scrolls near it. Many platforms do this by default.
- Never lazy-load the main image. If your theme or an optimization plugin lazy-loads everything, the image at the top of the page gets delayed along with the rest, and LCP suffers. Look for a setting to exclude the first image or the featured image. If you can edit the HTML, adding
fetchpriority="high"to that one image tells the browser to fetch it early.
If you're still choosing how to make post images, the guide to creating blog graphics on a small budget covers sizing and export settings.