By Rakibul Hasan, Moonlab
Core Web Vitals are three measurements Google uses to describe how a page feels to a real visitor: how fast the main content appears (LCP), how quickly the page responds to taps and clicks (INP) and how much it jumps around while loading (CLS). Passing them helps users and is a minor part of Google's page experience signals.
This guide explains each one in plain terms, shows how to test your site with free tools and lists the fixes that most often help small business sites. Google can change the metrics and thresholds, so check web.dev for the current ones. A fast site will not fix weak content, but a slow one loses visitors before they read it.
What Core Web Vitals are
Core Web Vitals are Google's way of measuring real world user experience on a page. They are collected from real Chrome users, which is why they are called field data. Lab tests simulate a load on a test device and are useful for debugging.
Google has said that page experience is one factor among many in ranking, and that relevant content still matters most. Treat speed as a quality and conversion task first, and an SEO bonus second.
LCP: Largest Contentful Paint
LCP measures how long it takes for the biggest visible element, usually a hero image or a large heading, to appear. Google's guidance is that a good LCP is 2.5 seconds or less. Check web.dev for the current thresholds.
The usual culprits are large uncompressed images, slow hosting, render blocking scripts and fonts that load late.
INP: Interaction to Next Paint
INP replaced the older First Input Delay as a Core Web Vital in March 2024. It measures how quickly the page responds visually after a tap, click or key press, across the whole visit. A good INP is generally 200 milliseconds or less.
Poor INP usually comes from too much JavaScript running on the main thread: heavy chat widgets, tracking scripts, page builders and sliders.
CLS: Cumulative Layout Shift
CLS measures unexpected movement of content as the page loads, such as a button that jumps just as you tap it. A good CLS is 0.1 or less.
It is caused by images and embeds with no set size, ads or banners that push content down, and web fonts that swap in late.
How to test your site
Start with PageSpeed Insights at pagespeed.web.dev. Enter a URL and read the field data at the top, if it is available, and the lab diagnostics below. Test your home page, a service page and a page that gets most traffic.
In Google Search Console, open the Core Web Vitals report under Experience. It groups pages by status for mobile and desktop and shows which issues affect the most URLs. Field data needs enough visitors, so a small site may show no data. In that case use the lab test and Chrome DevTools.
- Always test on mobile first.
- Test several pages, not only the home page.
- Re-test after each change, and give field data time to update.
Common fixes that work
Start with the cheap wins. Most small business sites gain the most from images and scripts.
- Compress images and use modern formats such as WebP or AVIF, at the size they are shown.
- Set width and height on images and embeds to prevent layout shift.
- Do not lazy load the main hero image, and preload it if needed.
- Remove plugins, widgets and tracking scripts you do not use.
- Load third party scripts after the page, or on interaction.
- Use a decent host and a CDN, and turn on caching.
- Limit fonts to one or two families and use font display swap.
Platform tips: WordPress, Shopify, builders
On WordPress, a heavy theme and many plugins are the usual problem. Remove unused plugins and use a caching plugin. On Shopify, apps add scripts, so review them. On builders like Wix or Squarespace you have less control, so focus on image size and removing extras.
If speed work is beyond your time, a developer can often fix the biggest items in a day or two. See moonlab.space/guides/website-audit-checklist-small-business for a wider check.
A worked example and common mistakes
Here is a made-up example. A bakery in Brighton runs a WordPress site with a large hero photo, a chat widget, a social media feed and eleven plugins. PageSpeed Insights on mobile shows a slow LCP, and Search Console lists many pages as needing improvement.
The owner works through the report in order. The hero photo is a 4 MB file shown at a small size, so she resizes it and converts it to WebP, and makes sure it is not lazy loaded. Images lower down get set width and height to stop the layout jumping. She removes four plugins she no longer uses, deletes the social feed, which few people clicked, and sets the chat widget to load only when a visitor clicks it. She turns on caching through the host.
She retests the same pages and compares the numbers. She also taps through the site on her phone. Field data in Search Console will take weeks to catch up, so she does not expect instant change there.
The steps above are usually enough for a small site. These are the common mistakes.
- Chasing a perfect score instead of fixing the biggest issue.
- Testing only the home page on desktop.
- Installing a speed plugin on top of a bloated theme.
- Lazy loading the main image, which delays LCP.
- Adding tracking scripts nobody checks.
- Uploading full size camera photos.
- Judging field data the day after a change.
How to decide and what to do this week
Use this order when you only have a few hours, because the first items usually give the largest gain.
- Resize and compress the largest image on each key page.
- Remove plugins, widgets and scripts you do not use.
- Set image dimensions to stop layout shift.
- Turn on caching and check your hosting plan.
- Defer chat widgets and tracking until after the page loads.
- Retest on mobile and write down the before and after scores.
How Moonlab can help
We test and fix speed issues as part of web builds and SEO work. See moonlab.space/services/web-development and moonlab.space/services/seo.
A free 30-minute automation audit at moonlab.space/contact is also open if you want a second pair of eyes.
