Core Web Vitals Basics: A Plain Guide for Irish Business Owners
Core Web Vitals are three measurements Google uses to judge 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 they read. They are called Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). You can check all three for free, and for most small business sites a handful of simple fixes does most of the work.
This guide is for owners of Irish small businesses, sole traders and tradespeople, not developers. You will learn what each metric means, what a good score looks like, where to see your own numbers, and which fixes are worth paying for.
TL;DR
- Core Web Vitals are three checks: loading (LCP), responsiveness (INP) and visual stability (CLS).
- A page counts as good when LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less, measured at the 75th percentile of visits.
- They are one signal among many. Good scores will not guarantee a top spot in Google, but poor ones lose visitors who are about to call or send an enquiry.
- Start with the free Search Console report and PageSpeed Insights, then remove what you do not need: unused plugins, old tracking scripts, oversized images.
Table of Contents
- What Core Web Vitals are, in plain words
- Do Core Web Vitals affect Google rankings?
- How Core Web Vitals are measured
- How to check your own site: a 15-minute routine
- A checklist of fixes, in order of payoff
- What is realistic for a small business site
- Our perspective: speed is a trust issue first
- When to fix it yourself and when to get help
- How we can help
- A simple monthly habit
- FAQ
- Sources
What Core Web Vitals are, in plain words
Google describes Core Web Vitals as a set of metrics that measure real-world user experience for loading performance, interactivity and visual stability. Think of them as a health check for the visitor’s experience of your site, not for how clever your site is underneath.
The idea was introduced by Google in 2020 as a common set of signals that matter to every website. The metrics have been refined since. INP replaced the older First Input Delay measure as the responsiveness metric, which is why some older articles list a different third metric. If you read a guide that mentions FID, it is out of date.
The three metrics
| Metric | What it asks | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long until the biggest thing on screen, usually a hero image or headline, is visible? | 2.5 seconds or less | Over 4 seconds |
| INP (Interaction to Next Paint) | When someone taps a menu or button, how quickly does the page visibly respond? | 200 milliseconds or less | Over 500 milliseconds |
| CLS (Cumulative Layout Shift) | Does the layout jump while the page loads? | 0.1 or less | Over 0.25 |
The thresholds above are the figures Google publishes for each metric. Anything between good and poor sits in the “needs improvement” band.
LCP: does it load quickly?
LCP times how long the largest visible element takes to appear. On a plumber’s homepage that is probably the banner photo. On a solicitor’s page it might be the main headline. If a visitor on a phone in rural Mayo sees a blank screen for four seconds, they will not stay to admire your services.
The usual culprits are huge uncompressed photos, slow hosting and too many things loading before the main content.
INP: does it respond when I tap?
INP watches the taps, clicks and key presses during a visit and reports how long the page took to react. A slow score feels like tapping “Call us” and nothing happening, so you tap again.
Google’s guidance for business decision-makers says that improving it often means reducing the load on the browser’s main thread. In practical terms that means removing heavy widgets, plugins and tracking tags, not trying to squeeze more speed out of them.
CLS: does the page stay still?
CLS adds up unexpected movement. You have met it: you go to tap one link, an image loads above it, everything slides down and you tap an advert instead. It is annoying on a news site and costly on a contact page, where a shifting button can mean a lost enquiry.
Many shifts happen because a template does not reserve space for content that loads late, such as images or ads. Setting sizes for images and embeds fixes most of it.
Do Core Web Vitals affect Google rankings?
Yes, but with sensible expectations. Google says its ranking systems reward content that provides a good page experience, and that site owners should not fixate on one or two aspects. Core Web Vitals feed into that picture. They do not replace good content, a clear service description, reviews and a well-set-up Google Business Profile.
Two misunderstandings come up again and again:
- “A perfect score means number one.” It does not. Relevance still wins. A fast page that says nothing useful will not outrank a slightly slower page that answers the question.
- “I need 100 out of 100.” You do not. Hitting the good thresholds consistently matters more than chasing perfection, according to Google’s page experience guidance.
The stronger reason to care is the visitor. If your pages load slowly, jump around or lag, people leave before they enquire. That is true even if your ranking never changes. If your site gets visits but few calls, our guide to why a website is not getting enquiries covers speed alongside eight other common causes.
How Core Web Vitals are measured
This trips up many owners. The scores that count come from field data: measurements from real people visiting your site, collected through the Chrome User Experience Report. They are not a single test run from a laboratory.
In Google Search Console, the Core Web Vitals report groups your pages as Good, Needs improvement or Poor, separately for mobile and desktop. It uses the previous 28 days of data, so a fix you make today will take a few weeks to show fully.
The “75th percentile” part means that for a page to pass, three out of four visits need to hit the good threshold. One fast test on your office broadband does not prove anything. The experience on an average phone and an average mobile connection does.
A new site, or one with little traffic, may show “not enough data”. That is normal. Lab tests can still point out problems in the meantime.
How to check your own site: a 15-minute routine
You do not need developer tools. Here is a routine you can do over a cup of tea.
- Open Search Console. If your site is verified, open the Core Web Vitals report and look at the mobile tab first. Note how many URLs are Poor or Need improvement, and which metric is flagged.
- Run PageSpeed Insights on three pages. Test your homepage, your main service page and your contact page. Google’s Web Vitals learning pathway explains how it uses field data and lab data side by side.
- Read the top of the result first. The field data section at the top is what Google assesses. The lab diagnostics below it suggest causes.
- Test on your own phone. Use mobile data, not wifi. Tap the menu, scroll, open the contact form. Does anything lag or jump?
- Write down the three numbers (LCP, INP, CLS) for each page, with today’s date, so you can see whether changes help.
If you want a broader routine that covers backups, forms and updates as well, our five-check website maintenance checklist takes about 45 minutes.
A checklist of fixes, in order of payoff
For small business sites, the problems are rarely exotic. Work down this list in order.
1. Clear out what you do not use
This is the highest-impact, lowest-skill fix. Google’s business guidance points out that unused scripts from expired campaigns still have to be downloaded and run, which can hurt both loading and responsiveness. Look for:
- plugins you installed once and forgot
- chat widgets nobody answers
- old tracking or advertising tags from campaigns that ended
- sliders and animations that add nothing
- social feeds embedded in the footer
The same guidance suggests a “less is more” attitude to features. Each addition costs speed, so it should earn its place by bringing in enquiries.
2. Resize and compress images
A photo straight off a phone can be several megabytes. Your banner does not need that. Export images at the size they will actually display, use a modern compressed format where your platform supports it, and avoid placing a very large photo at the very top unless it matters. That top image is usually your LCP element, so it is the one to get right.
3. Reserve space so nothing jumps
Give images, videos, maps and embedded forms a fixed width and height, so the browser holds the space before they load. If your site builder or theme does not do this, it is worth asking the person who looks after your site to fix it. It is a template issue, not something you should have to fight page by page.
4. Check your hosting
Cheap, overloaded hosting can slow every page before any content loads. If the Search Console report shows slow LCP across the whole site, hosting is a prime suspect. Choose hosting that suits your audience, and keep your website software updated.
5. Be careful with ads and pop-ups
If you display ads or promotional banners, remember Google’s warning that overloading mobile pages can drive drop-off that costs more than the ad revenue. The same goes for cookie banners and pop-ups that push content around.
6. Re-test and be patient
After changes, re-run PageSpeed Insights straight away for lab results. Give Search Console around four weeks to reflect improvements in field data.
What is realistic for a small business site
A five-page site for a tradesperson, accountant or beauty salon has a big advantage: it is simple. Fewer pages, fewer scripts and fewer plugins mean fewer things that can go wrong. Many problems we see on slow small sites come from piling on extras, not from anything the business needed.
That is also a reason to think carefully about structure. Our guide to one-page versus multi-page websites explains when a smaller site is the better choice, and a lean site makes good scores much easier to hold.
If you sell in one town, do not multiply near-identical location pages. They add weight and thin content. Our piece on location page SEO shows three checks that keep them useful.
Our perspective: speed is a trust issue first
We build websites for new Irish businesses, and the way we think about Core Web Vitals is shaped by who our customers are. A sole trader who has just started up does not have time to read a performance report. They need a site that opens fast on a phone, makes the phone number easy to tap and does not wobble while someone is trying to book.
So we treat these metrics as a by-product of sensible decisions, not a separate project:
- Build lean from the start. Every feature has to help a visitor enquire. If it does not, it does not go in.
- Keep jargon out of the conversation. You should be able to ask “is my site fast on mobile?” and get a straight answer.
- Do not sell perfection. Nobody can honestly promise a top Google position from a speed score. What we can do is keep the site in the good range and keep it tidy as it grows.
- Watch for creep. Sites rarely become slow on day one. They slow down as plugins, tags and large photos are added over a year or two. Ongoing care is what stops that.
If your current site is slow and you suspect it is costing you calls, the honest first step is the free check above. If the numbers are poor across the board, rebuilding on a lean foundation is often cheaper than patching an overloaded site.
— niall
When to fix it yourself and when to get help
You can safely do these yourself: removing unused plugins you recognise, compressing images before uploading, and checking your numbers monthly.
Get help when:
- Search Console shows Poor across many pages and you do not know why
- the site was built years ago on a heavy theme and every fix breaks something else
- INP is poor and you cannot tell which script is responsible
- you are about to launch a campaign and need the landing page to be quick
On that last point, a focused page often performs better than a crowded homepage. Our article on homepage versus landing page for Irish SMEs explains how to decide.
How we can help
If you would rather not manage this yourself, we build and look after lean business websites for Irish firms. Our pricing page lists three build options: Launch Website at €499 one-off, Business Website at €799 one-off and Growth Website from €1,295 one-off. Website Care costs €29 per month, Business Growth Care €49 per month and Website Care + SEO Growth €99 per month. The ongoing plans cover hosting and technical care, so the tidy-up described above does not depend on you remembering to do it.
If your existing site is the problem, see our website redesign service. You can also browse our website and local SEO services to see how speed, local search and enquiry features fit together.
A simple monthly habit
Performance work is not a one-off. A short monthly routine is enough for most small businesses:
- Open the Search Console Core Web Vitals report and note any change in the Poor or Needs improvement counts.
- Run PageSpeed Insights on your homepage and your top service page.
- Ask what has changed on the site since last month: a new plugin, a new tracking tag, a new set of photos.
- Remove anything that is not pulling its weight.
- Keep a simple log of dates and scores.
If a score worsens, the cause is almost always something added recently. That makes problems far quicker to diagnose than a once-a-year check.
FAQ
What are Core Web Vitals in simple terms?
They are three measurements of how a page feels to use: how fast the main content appears (LCP), how quickly it reacts to taps and clicks (INP), and whether the layout stays still (CLS). Google bases them on real visitor data. Each has a good threshold you can aim for.
What is a good Core Web Vitals score?
Good means an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less, measured at the 75th percentile of visits. These thresholds are set by Google. Poor starts above 4 seconds for LCP, 500 milliseconds for INP and 0.25 for CLS.
How long do improvements take to show?
PageSpeed Insights lab results update straight away. The Search Console report uses the previous 28 days of data, so allow about a month before judging the effect of a fix.
Do small business websites need to worry about Core Web Vitals?
Yes, though not obsessively. Slow or jumpy pages cost you enquiries whatever Google does, and they are one of the signals in Google’s page experience guidance. Aim to sit in the good range, keep the site lean and check it monthly.
Sources
- Understanding Core Web Vitals and Google search results, Google Search Central
- Understanding Google Page Experience, Google Search Central
- Core Web Vitals report, Search Console Help
- Optimize Core Web Vitals for business decision makers, web.dev
- Introducing Web Vitals, Chromium Blog
- Improve your website with Web Vitals, Google for Developers