Page Speed and Core Web Vitals Explained for Small Businesses

Most of us have abandoned a website that took too long to load or jumped around just as we tried to tap a button. Your customers behave the same way. Page speed affects how visitors experience your site and, to a degree, how Google evaluates it.

The trouble is that speed is easy to talk about and hard to pin down. Testing tools show unfamiliar acronyms, colored scores and long lists of suggestions. This guide explains what page speed really means, what Google's Core Web Vitals measure, how to test your own site and which fixes most often make a difference.

What Page Speed Really Means

Page speed isn't a single number. A page loads in stages: the server responds, the first content appears, the main content shows up, and the page becomes ready to respond to taps and clicks. A page can do well at one stage and badly at another.

Measurements also come in two kinds. Lab data comes from a test run in a controlled, simulated environment, which is useful for diagnosing problems. Field data comes from real visitors on their own devices and connections, which shows what people actually experience. Both are useful, but they often disagree, and field data is closer to reality.

The Three Core Web Vitals

Core Web Vitals are a set of metrics Google created to measure key parts of user experience. According to web.dev, Google's guidance site for web developers, there are currently three:

• Largest Contentful Paint (LCP) measures loading: how long it takes for the largest image or block of text in view to appear. Good is 2.5 seconds or less; poor is more than 4 seconds.
• Interaction to Next Paint (INP) measures responsiveness: how quickly the page visibly responds after clicks, taps and key presses throughout a visit. Good is 200 milliseconds or less; poor is more than 500 milliseconds.
• Cumulative Layout Shift (CLS) measures visual stability: how much content unexpectedly moves around while the page is in use. It is a score rather than a time. Good is 0.1 or less; poor is more than 0.25.

Results between good and poor are labeled needs improvement. Google assesses each metric at the 75th percentile of visits, separately for mobile and desktop. In plain terms, a page passes a metric when at least three out of four visits meet the good threshold.

If you have read older articles, you may see a metric called First Input Delay (FID). INP replaced FID as a Core Web Vital on March 12, 2024, because it gives a fuller picture of how responsive a page feels.

Do Core Web Vitals Affect Google Rankings?

Google Search Central says Core Web Vitals are used by its ranking systems, as part of a broader set of page experience signals. It is equally clear that Google aims to show the most relevant content even when page experience is below par.

The sensible reading is that speed matters, but it doesn't outweigh useful, relevant content. Fast, helpful pages are the goal, and the experience your visitors have is reason enough to care.

How to Test Your Site

Google's PageSpeed Insights is the usual starting point. Enter a web address and it reports two things:

• Field data from the Chrome User Experience Report, gathered from real Chrome users over the previous 28 days
• Lab data from Lighthouse, an automated tool that loads the page in a simulated mobile or desktop setting and suggests improvements

Smaller or newer sites often don't have enough real-user data for an individual page. In that case PageSpeed Insights may show data for the whole site instead, or no field data at all, leaving you with lab results only.

If your site is verified in Google Search Console, its Core Web Vitals report groups your pages by status using field data. Other free testers, such as yourfast.site, can offer a second view.

A few tips make test results more useful. Test your most important pages, not just the homepage. Pay more attention to the individual metrics than to the overall 0 to 100 performance score. Run lab tests more than once, because results can vary from run to run.

Common Fixes

Most problems trace back to a handful of causes.

For slow LCP:

• Resize and compress large images, and consider modern formats such as WebP or AVIF
• Make sure the main image near the top of the page isn't set to lazy-load
• Improve server response time with better hosting, caching or a CDN
• Reduce stylesheets and scripts that make the browser wait before displaying content

For poor INP:

• Remove third-party scripts and plugins you no longer need
• Reduce heavy JavaScript, especially code that runs during loading
• Ask your developer to break long-running scripts into smaller tasks so the browser can respond to visitors in between

For high CLS:

• Give images and videos a width and height so the browser can reserve space for them
• Reserve space for ads, embeds and banners that load late
• Avoid inserting new content above what visitors are already reading
• Load web fonts carefully so the text doesn't jump when the font arrives

A Sensible Approach for Owners

1. Test your key pages on mobile first, since phones are often slower.
2. Note which metric is failing rather than chasing the overall score.
3. Fix the biggest problems first, often images and unnecessary scripts.
4. Retest in the lab right away, then allow up to 28 days for field data to reflect the change.
5. Recheck after any redesign or after adding new plugins, widgets or tracking tools.

Key takeaways

• Page speed has several stages, and real-visitor field data matters more than any single lab score.
• Core Web Vitals are LCP (2.5 seconds or less), INP (200 milliseconds or less) and CLS (0.1 or less), assessed at the 75th percentile of visits.
• Core Web Vitals are used in Google's ranking systems, but relevant content still comes first.
• PageSpeed Insights shows both field and lab data, and small sites may only see lab results.
• Images, third-party scripts and missing image dimensions cause many of the most common problems.

Sources

• web.dev: Web Vitals
• web.dev: How the Core Web Vitals metrics thresholds were defined
• web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12
• Google Search Central: Understanding Core Web Vitals and Google search results
• Google for Developers: About PageSpeed Insights
• web.dev: Optimize Cumulative Layout Shift