Skip to content

Home / Blog / Core Web Vitals for Small Business Websites: What to Measure

Web Development

Core Web Vitals for Small Business Websites: What to Measure and Fix

LCP, INP and CLS sound technical, but they describe three things your visitors feel: speed, response and stability. Here is how to check them and what to fix first. Setting a sensible budget for core web vitals early makes every later choice simpler. If core web vitals involves several people, nominate one person to collect feedback and make the final call. Good notes on core web vitals save hours later, especially when more than one person is involved in decisions.

By Ragnar Studio's12 October 20269 min read
Abstract workspace with a laptop showing speed gauges, a loading bar and a mobile phone preview

Core Web Vitals are three measurements Google uses to describe how a page feels to a real visitor: how fast the main content appears, how quickly the page reacts when someone taps, and whether things jump around while loading. For a small business owner in India, they matter because most of your visitors arrive on a mid-range phone and a patchy mobile connection. This guide explains the three numbers in plain words, how to check them, what usually goes wrong on WordPress and Shopify sites, and which fixes are worth your money first. Related reading: Interaction to Next Paint (INP).

Related reading and services: WordPress development company in India, how to speed up a WordPress website, website speed optimization tips, technical SEO checklist and website SEO audit.

What these three numbers actually mean

You do not need to be technical to understand them. Each one answers a simple question a visitor silently asks.

  • LCP (Largest Contentful Paint): how long until the biggest thing on the screen, usually a hero image or a heading block, is visible. It is the "is this page loading?" feeling.
  • INP (Interaction to Next Paint): how long the page takes to visibly respond after a tap, click or key press. It is the "did my tap work?" feeling. INP replaced the older First Input Delay metric in 2024.
  • CLS (Cumulative Layout Shift): how much the page jumps while loading. It is the "I was about to tap Call Now and the button moved" feeling.

Together they cover speed, responsiveness and stability. They are not a score for your whole business or your content. They only describe the experience of using the page.

The commonly published "good" thresholds

Google publishes target values, and they are measured at the 75th percentile of real visits. In simple terms, at least three out of four visits should meet the target for the page to count as good.

MetricGoodNeeds improvementPoor
LCP2.5 seconds or less2.5 to 4 secondsOver 4 seconds
INP200 milliseconds or less200 to 500 msOver 500 ms
CLS0.1 or less0.1 to 0.25Over 0.25

Check Google's own documentation now and then, because thresholds and metrics can change over time. The idea behind them stays the same: a page should show its main content quickly, respond promptly and stay still. When you look at core web vitals, compare scope and clarity first and price second. With core web vitals, consistency matters more than volume: a few well-made pieces beat many rushed ones.

Why small businesses should care, and how much

Google has said that page experience, including these signals, is one input among many in search ranking. It is not the main one. Relevant content, good titles, links and a clear match for the search still count for far more. A fast page with weak content will not outrank a slower page that answers the question better.

The stronger reason is plain business sense. A visitor who taps an ad or a Google result on a phone and waits several seconds often leaves. If your enquiries come from WhatsApp clicks, call buttons or a checkout, every second of waiting and every mis-tap costs you a little. So treat Core Web Vitals as a way to find real usability problems, not as a trophy.

Want this done for you? Ragnar Studio's handles Website Maintenance. See how it works or get a free quote.

How to measure them properly

There are two kinds of data, and mixing them up causes most of the confusion.

Field data comes from real Chrome users visiting your site over the previous 28 days. It reflects real phones, real networks and real behaviour. This is what Google uses to assess your pages. Lab data is a simulated test run once, from a fixed device and connection profile. It is useful for debugging because it is repeatable, but it is only a guess at what real users experience.

Here are the tools worth using:

  1. PageSpeed Insights: paste a URL and it shows field data at the top (if your site has enough traffic) and a lab test below. Look at the mobile tab first. Read the field section before the big coloured score.
  2. Google Search Console, Core Web Vitals report: groups your URLs into good, needs improvement and poor for mobile and desktop. It is the best way to see patterns across the whole site. It needs enough real visits, so a very new or low-traffic site may show nothing.
  3. Chrome DevTools and Lighthouse: for a developer to find the exact image, script or element behind a problem.
  4. Your own phone: open the site on mobile data, not office Wi-Fi, and tap around. If it feels slow to you, it is slow.

If PageSpeed Insights says "no data available", that usually means too few visits, not a broken site. In that case lean on the lab results and common sense, and check again after traffic grows. If you have not set Search Console up, our Google Search Console guide for beginners walks through it.

Typical causes on WordPress and Shopify sites in India

Most poor results trace back to a short list of causes. The same ones appear again and again.

  • Heavy images: a 3 MB photo straight from a phone camera or a designer's export used as the hero image. This is the most common cause of a slow LCP.
  • Sliders and carousels: they load several large images and a script library, often to show one slide that people rarely look at past the first frame.
  • Too many plugins or apps: every WordPress plugin or Shopify app can add scripts and styles to every page, even pages where it does nothing.
  • Third-party scripts: chat widgets, review pop-ups, analytics tags, ad pixels, heat maps and social feeds. Each one asks another server for files, and together they hurt INP badly.
  • Cheap or overloaded hosting: a shared server that responds slowly delays everything that follows. The server's first response time shows up directly in LCP.
  • Page builder bloat: pages built with many nested sections and add-on widgets create a very large page structure that a phone must process.
  • Web fonts: several font families and weights, loaded late, can delay text or make it shift when the real font arrives.
  • Images and banners without set dimensions: the browser does not know how much room to leave, so content jumps when they load. This is the classic cause of bad CLS.
  • Mobile network reality: many visitors are on 4G with variable signal, or on a budget phone with limited processing power. Pages that feel fine on a developer's laptop can struggle here.

Shopify stores tend to lose points to apps and large theme sections, since the platform itself is well optimised. WordPress sites tend to lose points to hosting, plugins and unoptimised media, because those choices are left to the owner. Share your references for core web vitals, including things you like and things you want to avoid. It helps to agree how success with core web vitals will be judged before the first draft appears.

Prioritised fixes, in the order that usually pays off

Start with the cheapest changes that affect the most pages, and stop when the numbers are good enough.

  1. Fix the hero image first. Resize it to the size it is actually shown at, compress it, and use a modern format such as WebP where your platform supports it. Do not lazy-load the main hero image, because that delays LCP.
  2. Set width and height on images, banners and embeds. This reserves space and usually fixes most CLS problems in one pass.
  3. Remove what you do not use. Delete unused plugins and apps, old tracking tags and duplicate analytics scripts. Fewer scripts help every metric.
  4. Replace or simplify the slider. A single strong image with a clear heading and a button loads faster and often converts better.
  5. Delay non-essential third-party scripts. Chat widgets and pop-ups can load after the page is usable or after the first interaction.
  6. Add caching. On WordPress, a good caching setup and a content delivery network can help noticeably. Test after each change, because aggressive settings can break forms and checkout.
  7. Review hosting. If the server is slow to respond even on a plain page, no amount of image work will fully fix it. Our guide on how to choose web hosting in India covers what to look for.
  8. Trim fonts. Use one or two families, only the weights you need, and let the text show immediately.

For a step-by-step list aimed at WordPress, see how to speed up a WordPress website. Make one change at a time and re-test, so you know what actually helped. Keep a backup before touching anything on a live store, and write down the numbers before you start so you can show the owner or your team what changed. A short note with the date, the page tested and the three results is enough.

What not to obsess over

Chasing perfection wastes money. A few things deserve less attention than they usually get.

  • The 100 score. The lab performance score is one simulated run and it varies from test to test. A site scoring in the seventies with good field data and happy customers is in better shape than one scoring 100 with no sales.
  • Desktop results. If most of your visitors are on phones, work on mobile first.
  • Every low-traffic page. Fix your home page, top service pages, top product pages and checkout before the old blog post nobody reads.
  • Tiny gaps. Going from 2.6 seconds to 2.4 seconds on LCP matters little to a person. Going from 6 seconds to 3 seconds matters a lot.
  • Removing useful tools to please a test. If a WhatsApp chat button brings you enquiries, keep it and load it sensibly rather than deleting it for a better number.

Also remember that a field data report is a rolling 28-day window. After you fix something, the report can take weeks to show the improvement, so do not panic if it does not turn green overnight.

When to do it yourself and when to get help

Some fixes are safe for an owner: compressing images before upload, removing unused plugins after a backup, and cutting a slider from the home page. Anything involving theme code, caching rules, script loading order or hosting migration is better handled by a developer, because a wrong setting can break checkout, forms or tracking.

There is also a case where you should not spend at all. If your site gets almost no traffic, the bigger problem is probably visibility or content, not these metrics. Fix the basics from a technical SEO checklist, publish useful pages, and revisit performance once visits grow. And if the site is old and built on a heavy theme, a rebuild may cost less than endless patching. Ask for a clear before-and-after report in any case, with the same pages tested on mobile.

A simple plan you can follow this month

  1. Run your home page and two key pages through PageSpeed Insights on mobile. Note LCP, INP and CLS from the field section.
  2. Open the Search Console report and write down which page groups are listed as poor.
  3. Fix images and set their dimensions.
  4. Remove unused plugins, apps and old scripts.
  5. Test the site on your own phone on mobile data, including forms, WhatsApp button and checkout.
  6. Wait a few weeks, then check the report again.

This sequence handles the large majority of common problems without any deep technical work. If the numbers stay poor after that, the cause is usually hosting, theme structure or a heavy third-party script, and that is the time to bring in a developer. Ask how core web vitals will be tested or checked before it is called finished. Your own words and real details make core web vitals stronger than generic text ever will.

Frequently asked questions

What are Core Web Vitals in simple words?

They are three measurements of how a page feels to use. LCP is how fast the main content appears, INP is how quickly the page reacts to a tap or click, and CLS is how much the layout jumps while loading. Google publishes target values for each, and they are based on real visits from Chrome users.

What are the good thresholds for LCP, INP and CLS?

The commonly published good values are LCP at 2.5 seconds or less, INP at 200 milliseconds or less, and CLS at 0.1 or less. They are judged at the 75th percentile of real visits. Google can update its guidance, so confirm on its documentation before you set targets for a project.

What is the difference between field data and lab data?

Field data comes from real visitors over roughly the last 28 days, on their own phones and networks. Lab data is a single simulated test on a fixed device. Field data shows what users really experience, while lab data is better for finding and debugging a specific problem because you can repeat it.

Why does PageSpeed Insights say no data for my site?

Field data appears only when enough real Chrome users have visited the page. New sites and low-traffic pages often have too little. It does not mean something is broken. Use the lab results for guidance, test on a real phone, and check again once your traffic has grown.

Will fixing these metrics improve my Google ranking?

Page experience is one signal among many, and relevance and content quality usually matter more. Better numbers can help at the margin, but the bigger gain is usually fewer visitors leaving and more people completing calls, WhatsApp clicks or purchases. Treat it as a usability improvement first and a ranking tweak second. Revisit core web vitals every few months, because needs, tools and expectations change over time. Start small with core web vitals, learn from the first results and then expand what works. A short checklist for core web vitals keeps everyone aligned and makes later changes easier to discuss.

What is the most common reason for slow LCP on Indian business sites?

Oversized hero images are the usual cause, followed by slow shared hosting and heavy page builder layouts. A photo of several megabytes shown on a phone screen is far more data than needed. Resizing, compressing and serving it in a modern format often brings the biggest single improvement.

How long until improvements show in Search Console?

The Core Web Vitals report uses a rolling 28-day window of real visits, so it can take several weeks to reflect a fix. Lab tests in PageSpeed Insights update immediately, so use them to confirm a change worked, then be patient with the field report before drawing conclusions.

Can I fix these scores myself or do I need a developer?

You can safely compress images, remove unused plugins after a backup, and simplify sliders. Caching rules, script loading, theme code and hosting changes are better left to a developer, since a wrong setting can break forms, tracking or checkout. Always take a backup first and test on mobile afterwards.

Want a clear before-and-after report for your own site? Share the URL on WhatsApp and we will review it through our website speed optimization guidance and tell you what is worth fixing.

Free quote

Tell us about your website

Fill this short form and send it on WhatsApp. We reply with questions or a quote. Nothing is charged on the website.

  • Takes about two minutes
  • Goes straight to Ragnar Studio's on WhatsApp
  • Prefer email? Write to info@ragnarstudio.com

By sending, you agree that Ragnar Studio's may reply on WhatsApp about this enquiry.

Ready to start your project?

Tell us what you need. We reply on WhatsApp with questions, next steps and a quote.