WEBSITE SPEED AND CORE WEB VITALS.
A slow or jumpy website loses customers before they read a word. Google measures that experience with three Core Web Vitals. Here is what they mean, how to test your own site for free, and the fixes that usually matter most on a small business site.
WHAT CHANGED RECENTLY
- Google treats back-button hijacking as spam — Blocking the browser back button is now a named spam practice.
This guide covers what stays true. The blog tracks the changes as they land.
THE THREE METRICS
Google describes Core Web Vitals as a set of metrics that measure real-world user experience for loading performance, interactivity and visual stability.2 Interaction to Next Paint (INP) replaced First Input Delay as a Core Web Vital in 2024.1
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading: when the main content appears [1] | 2.5 seconds or less [1][3] |
| Interaction to Next Paint (INP) | Responsiveness: how quickly the page reacts to taps, clicks and typing [1] | 200 milliseconds or less [1][3] |
| Cumulative Layout Shift (CLS) | Visual stability: how much the page jumps around while loading [1] | 0.1 or less [1][3] |
web.dev recommends measuring at the 75th percentile of page loads, separately for mobile and desktop.1 Search Console rates LCP up to 4 s, INP up to 500 ms and CLS up to 0.25 as “needs improvement” and anything above as “poor”.3
DO THEY AFFECT RANKINGS?
Google says good Core Web Vitals align with what its core ranking systems seek to reward, as part of a wider page experience.2 It is one consideration among many. A fast page with thin or unhelpful content won't outrank a better answer, so treat speed as a way to keep the visitors you already earn.
HOW TO TEST YOUR SITE
| Tool | What it shows | Watch out |
|---|---|---|
| PageSpeed Insights | Field data from real Chrome users (CrUX) plus lab data from Lighthouse, for mobile and desktop [4] | Field data covers a trailing 28-day period, so fixes take time to show; lab and field results can disagree [4] |
| Search Console Core Web Vitals report | Groups of similar URLs rated Good, Needs improvement or Poor, based on real-user data [3] | Small sites may see “No data available” when there isn't enough CrUX data [3] |
No field data yet? Use the lab results in PageSpeed Insights as a guide, and test your most important pages: home, services and contact.
COMMON SMALL-BUSINESS FIXES
- Shrink images. Compress photos and use modern image formats.5 A phone photo straight from the camera is usually far larger than the screen needs.
- Don't lazy-load the hero image. web.dev says never to lazy-load your LCP image, and the
fetchpriorityattribute can tell the browser which resources matter most.5 - Give images and embeds a size. Include
widthandheightattributes, or reserve space with CSSaspect-ratio, so content doesn't shift.6 - Plan for web fonts. Font swaps can move text around as the font loads; choose a close fallback font.6
- Cut third-party scripts. Chat widgets, trackers and embeds add up. web.dev says to remove a script if it doesn't add clear value, and to load third-party scripts asynchronously unless they must run before the page renders.7
- Keep click handlers light. For INP, web.dev advises doing as little work as possible in event callbacks and breaking up long tasks.8
- Use decent hosting and a CDN. web.dev recommends a content delivery network to reduce the distance files travel.5
Speed is one part of a usable site. Our website accessibility guide covers the other half: people using keyboards, screen readers or zoom.
FAQ
My PageSpeed score is low but Search Console says Good. Which is right?
Both can be. The score comes from a simulated lab test; Search Console uses real visitors over time. Google explains that lab and field data can differ.4
Do I need a perfect 100?
No. Aim for the “good” thresholds above on your key pages, then spend your time on content and customers.
Will a faster site guarantee more leads?
No one can promise that. Speed removes friction; your offer, reviews and follow-up still do the selling.
SOURCES
- web.dev, Web Vitals.
- Google Search Central, Understanding Core Web Vitals and Google search results.
- Search Console Help, Core Web Vitals report.
- PageSpeed Insights documentation, About PageSpeed Insights.
- web.dev, Optimize Largest Contentful Paint.
- web.dev, Optimize Cumulative Layout Shift.
- web.dev, Efficiently load third-party JavaScript.
- web.dev, Optimize Interaction to Next Paint.
KEEP READING
BOOK A STRATEGY CALL
Not sure why your site feels slow? Send us the link and we will walk through what is holding it back.