How to Pass Google’s Core Web Vitals: A Speed Guide for Non-Techies

You pay for a website, launch it, and assume the hard part is done. Then the enquiries stay flat, your Google visibility never really improves, and on mobile the site still feels slow or awkward to use. That is where Core Web Vitals matter.

Google uses Core Web Vitals to measure how real people experience your site: how fast it loads, how stable it feels, and how quickly it responds when someone taps or clicks. If your site fails those tests, you are not just dealing with a technical issue. You are losing trust, conversions, and often rankings too. We see this constantly when we audit small business websites across Almería, Murcia, Alicante, and Granada.

What are Core Web Vitals in plain English?

Core Web Vitals are Google’s way of checking whether your website feels good to use for real visitors, especially on mobile.

They focus on three things:

• LCP: how quickly the main content appears
• CLS: whether things jump around while loading
• INP: how quickly the site responds when someone interacts with it

If you want the non-technical version, think of it like this:

• LCP asks: “How long until the page looks ready?”
• CLS asks: “Does the page stay still, or does it wobble about?”
• INP asks: “When I tap something, does it respond straight away?”

That matters because visitors do not think in technical terms. They think:

• “This site is slow.”
• “This page is annoying.”
• “I can’t click that properly.”
• “I’ll try another business instead.”

For a local business in Spain, that can mean a lost table booking, property enquiry, holiday rental booking, or quote request. We have audited plenty of sites where the design looked acceptable on desktop, but the mobile experience was bad enough to cost real business.

If you only do one thing today, test your homepage on mobile and pay attention to where it feels slow, jumpy, or hesitant.

Why Core Web Vitals affect rankings

Core Web Vitals are not the only ranking factor. Good content, relevance, backlinks, and local SEO still matter. But when two businesses are otherwise similar, speed and usability can help decide who performs better.

Google has been clear for years that page experience matters. Core Web Vitals are part of that. They do two jobs at once:

1. They help Google measure whether your site gives visitors a decent experience.
2. They directly affect what your visitors do after landing on the page.

That second point is often more important than the ranking signal itself.

If your page loads slowly, people leave.
If the layout shifts, people get frustrated.
If buttons take too long to respond, people stop trying.

So even if you only cared about leads and not rankings, you would still want to fix Core Web Vitals.

The business impact is usually bigger than the SEO impact

A lot of business owners hear “ranking factor” and think only about Google positions. The real issue is conversion.

For example:

• A restaurant site that takes too long to show the menu loses impatient mobile users.
• A solicitor’s site with shifting content causes accidental taps on the wrong link.
• A holiday rental site with slow image loading makes visitors doubt the quality of the property.
• An estate agency site that freezes when filtering listings feels untrustworthy.

This is exactly why our web design services are performance-first. We build in Astro, not WordPress, because pre-rendered pages are easier to keep lean, stable, and fast. On the right project, that is how we consistently hit 100/100 Lighthouse scores and first contentful paint under 0.4 seconds instead of leaving clients with another heavy theme to manage.

Treat Core Web Vitals as a conversion problem first and an SEO problem second. That mindset leads to better decisions.

The three Core Web Vitals explained simply

Each metric points to a different kind of weakness. Before you change anything, work out which metric is failing, because the fix for a slow page is not the same as the fix for a jumpy or unresponsive one.

LCP: Largest Contentful Paint

What it means: how long it takes for the main visible part of the page to load.

Usually that is your hero image, large heading, or main content block near the top of the page.

Good score: 2.5 seconds or less
Needs improvement: 2.5 to 4 seconds
Poor: more than 4 seconds

What LCP looks like in real life

Imagine someone searches “accountant in Almería” and taps your site. They expect to see the headline, main image, and first bit of useful content quickly. If they stare at a blank or half-loaded screen for several seconds, your LCP is likely poor.

Common reasons LCP is slow

• Oversized images
• Cheap or overloaded hosting
• Bloated themes and page builders
• Too many scripts loading before the main content
• Slow server response
• Heavy WordPress setups with too many plugins

WordPress is not automatically the problem, but many small business WordPress sites end up slow because they are running a page builder, a stack of plugins, and low-cost hosting all at once. That combination is common, and it is exactly why so many owners feel stuck.

This is one reason we often build static sites instead of bloated CMS setups. Our websites are pre-rendered HTML delivered via Cloudflare’s edge network, which removes a lot of server-side drag and helps us keep load times extremely low across Spain, including on weaker mobile connections.

Next step: open your homepage on your phone and ask yourself whether the main headline and first useful content appear almost immediately. If not, start with LCP.

CLS: Cumulative Layout Shift

What it means: whether things move around on the page while it loads.

Good score: 0.1 or lower
Needs improvement: 0.1 to 0.25
Poor: more than 0.25

What CLS looks like in real life

You go to tap “Call now” and just as your finger lands, an image loads late and pushes the button down. You hit the wrong thing. That is layout shift.

It is one of the most irritating website problems because it makes a site feel sloppy and untrustworthy.

Common reasons CLS happens

• Images without set dimensions
• Cookie banners appearing and pushing content down
• Fonts loading late and changing text size
• Ads, popups, or booking widgets injected above content
• Poorly built mobile menus

For local businesses, CLS is often worst on older WordPress sites packed with plugins, popups, and third-party widgets. We see it a lot on restaurant, property, and service business websites that have had “just one more plugin” added for years.

Next step: tap through your site on mobile and watch the first few seconds carefully. If buttons or text jump after the page appears, focus on CLS before anything else.

INP: Interaction to Next Paint

What it means: how quickly your site responds when someone clicks, taps, or types.

Good score: 200 milliseconds or less
Needs improvement: 200 to 500 milliseconds
Poor: more than 500 milliseconds

INP replaced First Input Delay as Google’s main interaction metric because it gives a better picture of how responsive a page feels.

What INP looks like in real life

A visitor taps:

• the mobile menu
• an enquiry form field
• a filter button
• a date picker
• a WhatsApp contact button

If nothing happens straight away, or the page hesitates before responding, your INP is likely weak.

Common reasons INP is poor

• Too much JavaScript
• Heavy themes and visual builders
• Chat widgets, trackers, and third-party scripts
• Complex booking engines
• Long-running browser tasks that block interaction

This is where many non-technical business owners get caught out. The site may look modern, but behind the scenes it is overloaded. A flashy design is useless if the user taps and waits.

When we improve this for clients, the biggest wins usually come from simplifying the front end and moving the heavy lifting to the back end. For example, we keep forms fast on the page itself, then push submissions into n8n or Make.com workflows afterwards so confirmations, notifications, and lead routing happen without slowing the site down.

Next step: test your mobile menu, form, and main call-to-action button on an actual phone. If they feel delayed, you likely have an INP problem.

What scores should you aim for?

If you want the simple answer, aim for all three of these:

• LCP: 2.5s or less
• CLS: 0.1 or less
• INP: 200ms or less

Those are Google’s “good” thresholds.

If your site hits all three consistently, you are in a strong position. If one is failing, fix that first. If all three are poor, the issue is usually structural rather than a quick setting you can change.

Do not obsess over a perfect lab score if your real-user data already passes. The goal is not bragging rights; it is a site that feels reliably fast for actual customers. If you want a deeper explanation of why this matters, our posts on why your website speed matters in Spain and performance-first web design in 2026 fit closely with this guide.

How to check your website with PageSpeed Insights

The easiest way to check your site is with Google PageSpeed Insights.

Go to: https://pagespeed.web.dev/

Then:

1. Enter your website URL
2. Click Analyse
3. Review the mobile report first
4. Look for the Core Web Vitals section
5. Check whether Google says the page passes or fails

What to look at first

Do not get distracted by every technical detail on the screen. As a business owner, focus on these areas:

1. Does the page pass Core Web Vitals?

This is the big one. Google will often show a clear pass or fail based on real-world user data when enough data exists.

2. What are the LCP, CLS, and INP numbers?

Compare them to the target scores above.

3. Are you looking at field data or lab data?

This is important.

• Field data = what real users experienced on your site over time
• Lab data = a test simulation done right now

Field data matters more because Google uses real-user experience. Lab data is still useful because it helps diagnose problems, but it is not the full picture.

4. Check mobile before desktop

A lot of websites look fine on desktop and perform badly on mobile. Google cares about mobile-first performance, so you should too.

Also check Google Search Console

If your site is connected to Search Console, open the Core Web Vitals report. This groups affected pages and shows whether the issue is poor LCP, CLS, or INP.

That helps you see whether the problem affects:

• just one page
• a page type
• or your whole website

For example, if all service pages are slow, that suggests a template or build issue. If only blog posts shift around, it may be an image or ad layout problem.

Run your homepage, one key service page, and your main contact or booking page today. That is usually enough to spot whether the problem is isolated or site-wide.

The most common reasons local business websites fail

Across audits we do for businesses in Almería, Murcia, Alicante, and Granada, the same problems come up again and again.

1. Massive images uploaded straight from a phone or camera

A homepage image does not need to be 6MB. Yet we still see it all the time.

Fix:

• compress images properly
• use modern formats like WebP or AVIF
• serve the correct image size for each screen

2. Page builders doing too much work

Many low-cost sites are built with drag-and-drop tools that load huge amounts of code for very simple layouts.

Fix:

• simplify the design
• remove unnecessary effects
• rebuild properly if the structure is fundamentally bloated

3. Too many third-party scripts

Chat widgets, cookie tools, analytics, booking plugins, social feeds, review widgets, tracking pixels — each one adds weight and delay.

Fix:

• keep only what genuinely helps the business
• delay non-essential scripts
• remove vanity features

4. Bad hosting

If the server is slow, everything starts badly.

Fix:

• use reliable hosting or edge delivery
• avoid ultra-cheap shared setups
• reduce backend dependence where possible

This is one reason our static-site approach works so well. When there is no heavy database and no plugin stack to process on every visit, there is far less to go wrong. If you are comparing approaches, our guide on static sites vs WordPress for small businesses in Spain is worth reading.

5. Layout instability from banners and popups

Cookie notices and promos are often added without thinking about page stability.

Fix:

• reserve space properly
• avoid injecting large elements above existing content
• keep popups minimal on mobile

If you recognise two or three of these issues on your site at once, assume you are dealing with a build problem rather than a simple setting you missed.

What you can do yourself — and when you need help

Some improvements are simple. Some are not.

You can often do these yourself

• Resize and compress large images
• Remove unnecessary plugins or widgets
• Cut back autoplay videos
• Reduce the number of fonts
• Check mobile pages in PageSpeed Insights regularly

You probably need expert help if

• your whole site fails all three metrics
• you use a bloated theme or builder and performance is poor across the board
• mobile interactions lag badly
• layout shifts happen throughout the site
• your hosting and site architecture are the real bottlenecks

A good rule: if you make the obvious fixes and the site is still slow, stop patching and look at the underlying setup.

The plain-English fix for each metric

Use the failed metric in PageSpeed Insights as your starting point. Otherwise, you risk spending money on the wrong fix.

How to improve LCP

If your main content appears too slowly:

• shrink your hero image
• remove heavy sliders and video backgrounds
• use better hosting or a static setup
• load the main content before non-essential extras
• reduce the number of large files at the top of the page

If the site still feels slow after image optimisation, the issue is usually deeper than media alone. That is often the point where a lighter build becomes the smarter option.

Business takeaway: your page should look useful almost immediately. If a visitor has to wait to understand what you do, you are already behind.

How to improve CLS

If the page jumps around:

• define image and video dimensions
• make sure banners and widgets have reserved space
• avoid injecting elements above content after load
• load fonts properly
• simplify mobile layouts

If your cookie banner, booking widget, or promo popup is causing the shifting, remove or redesign that before changing anything else.

Business takeaway: visitors should never have to fight your page just to click a button.

How to improve INP

If taps and clicks feel delayed:

• reduce JavaScript-heavy features
• remove unnecessary plugins and scripts
• simplify forms, filters, and menus
• keep third-party tools under control
• avoid building everything with heavy visual effects

For businesses that need fast follow-up, we usually keep the website itself lean and handle the admin behind the scenes. That might mean sending form leads into an n8n workflow, notifying the right team member instantly, or triggering a booking confirmation sequence in Make.com. The point is simple: the workflow should do the repetitive work, not the browser.

Business takeaway: when someone taps “Book now”, “Call”, or “Send enquiry”, your site should respond instantly.

For businesses that also want to automate what happens after those enquiries come in, this often overlaps with our business automation services too. A fast website gets the lead; a good workflow makes sure you do not lose it afterwards.

Should you rebuild instead of trying to patch the site?

Sometimes yes.

If your site is old, plugin-heavy, badly hosted, or built on a bloated page builder, spending months patching performance can cost more than replacing it properly.

A rebuild makes sense when:

• the site is more than a few years old and hard to maintain
• every fix creates another problem
• mobile performance is consistently poor
• SEO foundations are weak
• the website still does not convert even when traffic arrives

We are honest about this with clients. Not every site needs a rebuild. But plenty do. In those cases, patching is just paying to keep an inefficient setup alive.

That is why CostaDelClicks builds lean, fast, bilingual websites from the ground up, with proper hreflang, strong mobile performance, and no plugin bloat. If you serve both English and Spanish-speaking customers, that matters even more. We build both language versions natively rather than adding translation as an afterthought, which avoids the usual SEO and script-heavy translation-widget problems. Our related guide on should your website be bilingual? is a useful next read.

Compare the cost of months of patching with the cost of replacing a weak foundation. That is usually where the right answer becomes obvious.

A simple Core Web Vitals checklist for business owners

Before you spend money, run through this list:

• Check your homepage in PageSpeed Insights
• Check the mobile results first
• Note your LCP, CLS, and INP scores
• See whether the page passes or fails Core Web Vitals
• Test your main service pages too
• Look in Search Console for patterns across the site
• Identify heavy images, scripts, and widgets
• Remove anything that does not help leads or sales
• Decide whether the site needs optimisation or a full rebuild

If you want a broader view of local performance and visibility, our guides on local SEO for small businesses in Spain and performance-first web design in 2026 are the next logical step.

Keep this checklist beside you while reviewing PageSpeed Insights and Search Console. It stops you getting lost in the technical noise.

The bottom line

Core Web Vitals are not just a Google box to tick. They are a simple way to measure whether your site feels fast, stable, and easy to use.

If your website loads slowly, shifts around, or lags when people tap, you are making it harder for customers to trust you. That hurts rankings, but more importantly, it hurts enquiries.

The good targets are straightforward:

• LCP: 2.5 seconds or less
• CLS: 0.1 or less
• INP: 200 milliseconds or less

Check your site in PageSpeed Insights. Look at mobile first. Focus on real-user data where available. And if your website is failing badly, do not assume the fix is just a plugin or a checkbox. Often the problem is the way the site was built in the first place.

Test the site this week, and if the results are poor, get a second opinion before spending money on cosmetic fixes that leave the real bottleneck untouched.

Frequently asked questions