Core Web Vitals are three scores from Google that show how a page feels to real visitors: how fast the main content shows, how fast the page reacts to a tap, and how much it jumps while it loads. Here is Core Web Vitals for beginners in one line: show the main content within 2.5 seconds, react within 200 milliseconds and keep the layout shift score at 0.1 or less.
The Website SEO Checkup groups these scores with a few speed checks, such as blocking scripts, file size and server time. This guide explains each one in plain words and shows you what to change.
What are the three Core Web Vitals?
Each score has a long name, so most people use the short letters. Here is what they mean:
| Score | What it measures | Good result |
|---|---|---|
| LCP (Largest Contentful Paint) | When the biggest image or text block shows | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How fast the page reacts to a tap, click or key press | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the page jumps while it loads | 0.1 or less |
Google looks at the 75th percentile of visits, on phones and on desktops. In plain words, at least three out of four visits should get a good result. A page passes only when all three scores are good.
Where do the numbers in the checkup come from?
There are two kinds of speed data. Lab data comes from one test run on a simulated phone. Field data comes from real Chrome users who visited your page over the last few weeks. Small sites often have no field data yet, because too few people visit.
The PageSpeed score in the checkup is a lab score. It sums up how fast the page loads on a mid-range phone. It also shows helper numbers:
- First Contentful Paint (FCP): when the first text or image shows up.
- Total Blocking Time (TBT): how long scripts keep the page from reacting. A lab test has no real person tapping, so it cannot measure INP. Google suggests TBT as a stand-in.
- Time to First Byte (TTFB): how long your server thinks before it sends the first piece of the page.
Field data shows up in PageSpeed Insights and in the Core Web Vitals report in Google Search Console, once your site has enough visits.
Do Core Web Vitals help you rank?
Google says it highly recommends good Core Web Vitals for success with Search. It also says they match what its core ranking systems try to reward. Still, a fast page with weak content will not beat a slower page that answers the question better. Treat speed as a tie-breaker and a kindness to visitors.
I learned this the expensive way. I once paid for a hosting plan sold as many times faster than normal. I felt no difference on my own sites. Today I think clean pages and small files matter more than a hosting label.
Core Web Vitals for beginners: which score to fix first?
Start with LCP. It is the score most sites fail, and the fixes are simple. Then fix CLS, and leave INP for last. Most small blogs pass INP once they cut extra scripts.
How do you fix a slow LCP?
- Run the page in PageSpeed Insights and look for the "Largest Contentful Paint element". It is often the cover image or the first heading.
- If it is an image, resize it to the size it is shown at and save it as WebP. The Image to WebP Converter does both in your browser.
- Do not lazy-load that one image. Remove
loading="lazy"from it and addfetchpriority="high"instead. - Stop scripts from blocking the page. A blocking script is one in the head that the browser must load before it shows anything. Add
deferto each one that does not need to run first, like this:<script src="/js/menu.js" defer></script> - Minify your files. Minify means removing spaces and comments so the file gets smaller. Use the CSS Minifier and Unused CSS Checker for your style sheets.
A slow TTFB on every page usually points to slow hosting, a slow database or no page caching. On WordPress, a caching plugin helps. The Bloghints CMS caches pages on its own. Text compression also cuts download time, and our guide on how to enable gzip and browser caching shows the .htaccess lines.
How do you stop the page from jumping (CLS)?
Layout shift happens when something loads late and pushes the text down. You start to read, and the line jumps away. Here is how to stop it:
- Give every image a width and a height:
<img src="/images/cake.webp" width="800" height="450" alt="Chocolate cake"> - Keep space for ads and embeds with a fixed minimum height in your CSS.
- Do not add banners or cookie bars above the content after the page has loaded.
- Move things with the CSS transform property, not with top, left or margin.
Our guide to image SEO for beginners covers image sizes, alt text and WebP in more detail.
How do you make taps feel faster (INP)?
INP gets worse when the browser is busy running JavaScript, the code that makes menus, sliders and ads work. While it runs, the page cannot answer a tap. These steps help:
- Remove plugins, widgets and tracking tags you no longer use.
- Load the rest with
defer, so they run after the page shows. - Check your scripts with the JS Minifier and Cleaner and shrink them.
- Press F12, open the Console tab and fix red errors. Broken scripts can freeze menus and forms. Old plugins and ad code are the usual cause.
- Keep the page structure small. Very long pages with thousands of tags (the DOM) slow every tap. Split long lists into pages.
What about page size, requests and load time?
The checkup also counts how big your HTML is, how many files the page asks for and how long it takes to load. Each file is one more trip to the server. Move large blocks of inline CSS and JavaScript into their own files. Merge small files where you can. Lazy-load images that sit below the first screen, but never the main image at the top.
You do not need a perfect score of 100. A page that loads its main content fast, stays still and reacts quickly is good enough for visitors and for Google.
How do you check that your fixes worked?
- Clear your site cache or your caching plugin cache.
- Run PageSpeed Insights again on the same page, on the mobile tab.
- Open the page on your own phone and scroll. Watch for jumps.
- In Search Console, open Core Web Vitals. Field data moves slowly, so give it a few weeks before you judge.
Fix one template at a time, such as your post layout, because one change then helps every post. That is the core of Core Web Vitals for beginners: small images, fewer scripts and fixed sizes. When you are done, re-run the free Website SEO Checkup to see which speed items now pass.
Frequently asked questions
Why is my PageSpeed score different every time I test?
Lab tests run on a simulated phone and network, and small changes in server load or ads change the result. Run the test two or three times and look at the middle score. Watch the trend over weeks, not a single run.
Does my site fail if it has no field data?
No. Field data only appears when enough real Chrome users visit a page. Small sites often see "no data" in Search Console. Use the lab numbers from PageSpeed Insights as your guide until real data shows up.
Will better hosting fix my Core Web Vitals?
It can help a slow server time, but it rarely fixes everything. Big images, blocking scripts and missing image sizes cause most problems, and they stay the same on any host. Fix the page first, then move hosts only if your server is still slow.
