A good website loading speed means your main content appears within 2.5 seconds, the page reacts to a tap or click within 200 milliseconds, and nothing jumps around while it loads. Those are Google's three Core Web Vitals, and they are the closest thing there is to an official definition of a fast website.
Speed matters because people leave slow pages, especially on phones. It also matters to Google, which says good Core Web Vitals align with what its ranking systems seek to reward.
This guide explains each of the three measures in plain English, how to test your own site for free, why small business sites are often slow, and what to fix first. It also covers why chasing a perfect score of 100 is usually a waste of time.
What a good loading speed actually means
"Loading speed" sounds like one number, but a page doesn't load in one moment. The text appears, then the photos, then the buttons start working. Google splits that experience into three parts and sets a target for each.
- Loading: the biggest thing on the screen should appear within 2.5 seconds.
- Responsiveness: the page should react to a tap, click or key press within 200 milliseconds.
- Stability: the layout shouldn't shift while you're reading or about to tap something.
Google measures these at the 75th percentile of real visits, split by mobile and desktop. In plain terms, at least three out of four visits need to hit the target. A page passes only when it meets all three.
The three Core Web Vitals explained
Largest Contentful Paint (LCP): how fast it loads
LCP is the time it takes for the largest image or block of text in view to appear. On most small business sites that's the hero photo or the main heading. Good is 2.5 seconds or less. More than 4 seconds is poor.
Interaction to Next Paint (INP): how fast it responds
INP measures the delay between a visitor tapping something, like a menu button or a form field, and the page visibly responding. Good is 200 milliseconds or less. More than 500 milliseconds is poor. INP replaced an older measure, First Input Delay, as a Core Web Vital on 12 March 2024, so older guides that mention FID are out of date.
Cumulative Layout Shift (CLS): how stable it is
CLS scores how much the page jumps around as it loads. You've seen it when you go to tap a link and an ad or image pushes it down at the last second. It's a score, not a time. Good is 0.1 or less. More than 0.25 is poor.
- Good: LCP 2.5 seconds or less, INP 200 ms or less, CLS 0.1 or less.
- Needs improvement: LCP up to 4 seconds, INP up to 500 ms, CLS up to 0.25.
- Poor: anything above those.
How to test your website speed
Two free Google tools tell you most of what you need. Neither needs any technical setup beyond a Google account for the second one.
PageSpeed Insights
Go to pagespeed.web.dev, enter your web address and run the test. Check the mobile tab first, because most local customers will find you on a phone. The top of the report shows whether your page passes the Core Web Vitals assessment. Further down is the performance score out of 100.
Google Search Console
The Core Web Vitals report in Search Console groups similar pages together and labels them Good, Need improvement or Poor, separately for mobile and desktop. When you fix a problem, you can ask Google to validate the fix, and it then tracks your pages over 28 days. If you haven't set up Search Console yet, our guide to why your website isn't showing up on Google walks through it.
Lab data vs field data
PageSpeed Insights shows two kinds of results, and they often disagree. Field data comes from real Chrome users who visited your site over the previous 28 days. Lab data comes from a single simulated visit run by a tool called Lighthouse. Field data is what Google uses for Core Web Vitals. Lab data is useful for finding what's slow and checking a fix straight away.
Why small business websites are slow
Slow sites rarely have one big problem. Usually it's a pile of small ones that build up over years. These are the usual suspects.
- Huge images: photos uploaded straight from a phone or camera, several times larger than the screen showing them. This is the most common cause of a slow LCP.
- Page-builder bloat: drag-and-drop builders and heavy themes load code for every feature they offer, whether your page uses it or not.
- Too many plugins and scripts: chat widgets, pop-ups, sliders, tracking tags and social feeds each add code the browser has to download and run. They are the usual cause of a poor INP.
- Cheap or overloaded hosting: if the server is slow to respond, everything after it is slow too, no matter how well the page is built. Our guide to what website hosting is explains what you are paying for.
- Things loading late: images without set sizes, web fonts and cookie banners that appear after the page has drawn cause the layout to jump, which hurts CLS.
If several of these sound familiar, the site may need more than a tune-up. Our list of signs your website needs a redesign can help you decide.
What to fix first
Start with whichever Core Web Vital is failing on mobile, and start with your most important pages: the home page, your main service pages and your contact page.
- If LCP is slow: resize and compress your largest images, especially the one at the top of the page. Then look at your hosting.
- If INP is slow: remove plugins, widgets and tracking scripts you don't use. Each one you cut is less work for the visitor's phone.
- If CLS is high: give every image and video a set width and height, and make sure banners and pop-ups don't push content down.
The payoff can be real. In an A/B test published on web.dev, Vodafone found that a 31% improvement in LCP led to 8% more sales, with no other changes to the page.
Some sites can't be fixed from the inside. If the slowness comes from the platform or theme itself, every fix is a patch on top of the problem, and a rebuild is often quicker and cheaper.
Common misconceptions about website speed
"I need a score of 100"
You don't. Google's Lighthouse documentation says a perfect 100 is extremely challenging to achieve and not expected. A score of 90 or above is rated good. Going from 99 to 100 takes about the same improvement as going from 90 to 94, which is effort better spent on your content.
"The score is what Google ranks"
It isn't. The performance score is a lab measure from a single test. What counts for Google is whether real visitors get a good experience, which is the Core Web Vitals field data. A page can have a middling lab score and still pass, or a high one and fail.
"A fast site will rank first"
Speed helps, but it isn't a shortcut. Google says it always seeks to show the most relevant content, even if the page experience is sub-par. A fast page that doesn't answer the search won't outrank a slower one that does.
"My score changed, so something broke"
Not necessarily. Lab scores change from run to run because of network conditions, ads, browser extensions and the device running the test. Look at the trend over several tests, and at the field data, rather than any single result.
So, to put it another way: a fast website is one where real visitors, most of them on phones, see your content quickly, can use it straight away and don't have it shift under their thumb. Pass all three Core Web Vitals and you're there. More questions about how we build and host sites are in our FAQ.
Key takeaways
- (01)
A good loading speed means LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
- (02)
Test with PageSpeed Insights on mobile and the Core Web Vitals report in Search Console. Field data from real visitors is what counts.
- (03)
Most slow small business sites come down to huge images, page-builder bloat, too many scripts and cheap hosting.
- (04)
Aim to pass all three Core Web Vitals and score 90 or above. A perfect 100 is not expected and rarely worth the effort.
Frequently asked questions
How fast should my website load?
The main content should appear within 2.5 seconds, the page should respond to taps within 200 milliseconds, and the layout should stay stable with a CLS score of 0.1 or less. Google checks this for at least three out of four real visits.
What is a good PageSpeed Insights score?
90 or above is rated good, 50 to 89 needs improvement, and below 50 is poor. The score is a lab test, though. Whether your page passes the Core Web Vitals assessment matters more than the number.
Does website speed affect Google rankings?
Yes, as one of many signals. Google says good Core Web Vitals align with what its ranking systems reward, but it will still show the most relevant page even if its experience is not as good.
Why is my website slow on mobile but fine on my computer?
Phones have less processing power and often slower connections, so large images and heavy scripts hurt more. PageSpeed Insights tests mobile separately for this reason. Start with the mobile results.
More answers on price, hosting and timing in our FAQ.