Core Web Vitals: why site speed wins customers

Core Web Vitals are three Google metrics — LCP, INP and CLS — that measure how fast, responsive and stable your pages feel to real visitors. They matter because a faster site keeps more people from bouncing, converts more of them into customers, and earns a small but real ranking advantage on Google. For most Canadian small businesses, fixing speed is one of the highest-return changes you can make to a website.

Key takeaways

• Core Web Vitals are three metrics: LCP (loading), INP (responsiveness) and CLS (visual stability).
• The targets to aim for are LCP under 2.5s, INP under 200ms, and CLS under 0.1 — measured on real mobile devices.
• Speed is a confirmed Google ranking factor, but its bigger payoff is conversions: slow pages lose visitors before they ever read your offer.
• The most common culprits are oversized images, heavy third-party scripts, and slow or oversold hosting.
• Measure with PageSpeed Insights and Search Console, prioritise the worst offenders, and re-test after each fix.
• How a site is built matters: lean, well-coded pages start far ahead of bloated template-and-plugin stacks.

What Core Web Vitals actually are

Core Web Vitals are Google's attempt to put a number on something every visitor feels but few can name: does this page feel fast and solid, or slow and janky? Rather than rely on a single "load time," Google breaks the experience into three distinct measures, each capturing a different moment in how a page comes to life.

The important thing to understand is that these are field metrics — ideally collected from real Chrome users visiting your site on real connections and real phones, not just a lab test on a fast office network. That is why a site can look quick on your desktop and still score poorly: Google is averaging the experience of people on mid-range Android phones and patchy mobile data, which is closer to how many Canadians actually browse.

LCP — Largest Contentful Paint

LCP measures how long it takes for the largest visible element — usually a hero image, headline or banner — to finish rendering. In plain terms, it is "how long before the page looks like it has loaded." A good LCP is under 2.5 seconds; anything past 4 seconds is poor, and visitors are already leaving.

INP — Interaction to Next Paint

INP replaced the older First Input Delay metric. It measures responsiveness: when a visitor taps a button, opens a menu or types in a field, how long before the page visibly responds? A good INP is under 200 milliseconds. Sluggish INP usually points to too much JavaScript running on the page.

CLS — Cumulative Layout Shift

CLS measures visual stability — how much the layout jumps around while loading. We have all tried to tap a link only for an ad or image to load late and shove everything down. A good CLS is under 0.1. It is often the easiest of the three to fix.

Why speed wins customers, not just rankings

It is tempting to treat Core Web Vitals as an SEO checkbox, but the real prize is conversions. Visitors form an impression of your business in the first second or two. A page that stalls on a blank screen, or shifts under their thumb, signals carelessness before you have said a word — and on mobile, an impatient visitor is one back-tap away from a competitor.

The relationship is direct: every second of delay tends to increase bounce rate and shrink the pool of people who reach your contact form or checkout. For a service business, that is fewer enquiries from the same ad spend. For a shop, it is abandoned carts. We dig into the full funnel in our guide to getting more leads from your website, but the short version is that speed multiplies the value of every other improvement you make.

Then there is the SEO layer. Google has confirmed that page experience — including Core Web Vitals — is a ranking signal. It will not vault thin content above great content, but when two pages are otherwise comparable, the faster, more stable one tends to win. Speed compounds with the fundamentals we cover in website SEO basics and local SEO for Canadian businesses, where mobile users dominate "near me" searches.

How to measure your Core Web Vitals

You cannot fix what you do not measure, and the good news is that the best tools are free. Start here:

• PageSpeed Insights — paste in any URL for both lab and (where available) real-user field data, plus a prioritised list of fixes.
• Google Search Console — the Core Web Vitals report groups your URLs into "good," "needs improvement" and "poor," based on real visitor data over the past 28 days.
• Chrome DevTools / Lighthouse — built into Chrome for quick lab tests and pinpointing which element is your LCP.

Lab data vs field data

This trips people up constantly. Lab data is a single simulated test — useful for debugging but not how Google judges you. Field data (the Chrome User Experience Report) reflects what real visitors experienced over the last month, and that is what feeds the ranking signal. Always test on a throttled mobile profile, because that is where problems hide. Our case for designing to the phone first is laid out in mobile-first design.

What slows a website down

In our experience auditing Canadian small-business sites, the same handful of issues account for the vast majority of poor scores. Knowing them helps you spend your time where it counts.

• Oversized images — a 4 MB photo straight off a phone or stock library is the single most common cause of slow LCP.
• Heavy third-party scripts — chat widgets, multiple analytics tags, pop-up builders, ad pixels and social embeds each add weight and hurt INP.
• Plugin and theme bloat — on template platforms, every plugin loads its own CSS and JavaScript, often on every page.
• Slow or oversold shared hosting — a cheap plan that crowds thousands of sites onto one server adds delay before your page even starts loading.
• No image dimensions set — the classic cause of layout shift, as content reflows when images finally appear.
• Render-blocking resources — large fonts and stylesheets that must load before anything is painted.

How your site was built sits underneath all of this. A lean, hand-coded site ships only the code it needs, while a stacked template-and-plugin build often carries kilobytes of unused weight. We compare the trade-offs in custom-coded vs WordPress, and the choice of host matters too — see choosing a domain and hosting in Canada.

How to improve each metric

Fixes map neatly onto the three vitals. Tackle them in order of impact rather than trying to do everything at once.

Improving LCP (loading)

• Compress and properly size images; never serve a 2000px photo into a 600px slot.
• Use modern formats like WebP or AVIF, which are far smaller than JPEG or PNG.
• Lazy-load images below the fold, but never lazy-load your hero/LCP image.
• Use a content delivery network (CDN) so files load from a server near the visitor.
• Move to faster hosting if your server response time is consistently high.

Improving INP (responsiveness)

• Audit and remove third-party scripts you do not truly need.
• Defer non-essential JavaScript so it does not block the main thread.
• Prefer lightweight CSS animations over heavy JavaScript effects — see how scroll animations improve conversions for doing this without the bloat.

Improving CLS (stability)

• Always set explicit width and height (or aspect-ratio) on images and videos.
• Reserve space for ads, embeds and banners so nothing pops in late.
• Preload web fonts and use font-display to avoid text reflow.

A practical speed-fix checklist

If you want a repeatable process rather than a pile of tips, work through these steps in order. Re-test after each one so you can see what moved the needle.

• 1. Baseline. Run PageSpeed Insights on your three most important pages (home, top service/product, contact) on mobile and record the scores.
• 2. Images first. Compress, resize and convert every large image. This alone fixes most LCP problems.
• 3. Cut the dead weight. Remove unused plugins, duplicate analytics tags and abandoned widgets.
• 4. Lock the layout. Set dimensions on all media and reserve space for anything that loads late.
• 5. Tame the scripts. Defer non-critical JavaScript and consolidate tracking through a single tag manager.
• 6. Check the foundation. Confirm caching and a CDN are active, and that your host is responding quickly.
• 7. Re-measure in Search Console. Field data updates over about 28 days, so give it time before judging the result.

If your site is years old and resists these fixes, the build itself may be the bottleneck. The warning signs are in 12 signs your business website needs a redesign, and you can rebuild for speed without losing rankings by following redesign without losing SEO.

Speed vs design: you don't have to choose

A myth worth retiring is that a fast site has to be plain. Rich visuals, smooth motion and a distinctive look are all compatible with strong vitals — the difference is craft, not compromise. The slow sites we see are rarely slow because they are beautiful; they are slow because images were never optimised and a dozen plugins were bolted on over the years.

Good performance is a design decision made early: choosing efficient formats, building reusable components, and resisting the urge to add every shiny widget. Done right, the same page that scores well on Core Web Vitals is also the one that converts — the principles overlap with what makes a high-converting homepage work in the first place.

Frequently asked questions

What is a good LCP, INP and CLS score?

Aim for LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, all measured on mobile. Google labels scores as "good," "needs improvement," or "poor," and you generally want all three pages in the "good" band based on real-user field data, not just a single lab test.

Do Core Web Vitals affect SEO?

Yes. They are part of Google's page experience signals and act as a tiebreaker between pages of similar quality. They rarely outweigh strong, relevant content on their own, but they help rankings at the margins and, more importantly, they directly improve conversions by keeping impatient visitors on the page.

What slows websites down the most?

Large unoptimised images are the number one culprit, followed by heavy third-party scripts such as chat widgets, ad pixels and duplicate analytics tags. Slow or oversold shared hosting and plugin bloat round out the list. Fixing images and trimming scripts usually delivers the biggest, fastest gains.

How do I test my Core Web Vitals for free?

Use Google PageSpeed Insights for a per-URL report with prioritised fixes, and Google Search Console for site-wide field data grouped into good, needs-improvement and poor. Chrome's built-in Lighthouse tool is handy for quick lab tests. Always test on a mobile profile, since that is how Google evaluates you.

How long until speed fixes show up in Google?

Lab tools show improvements immediately, but the field data Google uses for ranking is a 28-day rolling average of real visitors. Expect Search Console to reflect your changes over roughly three to four weeks. Conversion gains, however, often appear right away as bounce rates drop.

Is a custom-coded site faster than WordPress?

Not automatically, but it starts with an advantage. A lean, hand-coded site ships only the code it needs, while template-and-plugin builds often carry unused weight. WordPress can be made fast with disciplined optimisation; a poorly maintained one rarely is. The build quality and hosting matter more than the platform name.