Skip to content
SpeedCore Web VitalsSmall business

How fast should a website load in 2026? The targets and how to measure them

The speed targets that matter in 2026: LCP under 2.5 s, INP under 200 ms, CLS under 0.1. What each means, which test to trust, and what a good score looks like.

Published: 6 min read Asen Panayotov, B63

Short answer: on a phone, the main content of your page should appear within 2.5 seconds, the page should react to a tap within 200 milliseconds, and nothing should jump around while it loads. Those are Google’s three Core Web Vitals targets. If your homepage meets them on a mid-range phone, it’s fast enough; if it misses them, visitors notice before Google does.

“Fast” is vague, and speed tools throw a lot of numbers at you. This guide sets out the few targets that matter, how to test against them, and how to read the results without chasing a perfect score. If you already know your site is slow and want the causes and fixes, read why is my website slow on mobile instead.

The three numbers that matter

Google’s Core Web Vitals describe how a page feels to a real visitor. Each one has a “good” threshold, and a page passes when at least 75% of real visits meet it:

Metric The question it answers Good Poor
Largest Contentful Paint (LCP) How long until the main content, usually the big image or heading, is visible? 2.5 s or less over 4 s
Interaction to Next Paint (INP) When someone taps a button or opens the menu, how quickly does the page respond? 200 ms or less over 500 ms
Cumulative Layout Shift (CLS) Does the page jump around while loading? 0.1 or less over 0.25

Between “good” and “poor” is “needs improvement”. INP replaced the older First Input Delay metric in 2024, so if a guide still talks about FID, it’s out of date.

The 75% rule matters. A page that is fast on your office Wi-Fi but slow for a quarter of your visitors on mobile data doesn’t pass.

Why the phone is the test that counts

Most people looking for a local business search on their phone, often on mobile data, and phones have far less processing power than a laptop. A site that loads in a second on your desk can take several times longer on a mid-range phone. That’s why speed tests, including Google’s, simulate a phone on a slower connection by default. Judge your site by the mobile result, not the desktop one.

Lab tests and field data: which one to trust

You’ll see two kinds of numbers:

  • Field data comes from real Chrome users who visited your site over the last 28 days. It’s what Google uses for ranking, and it’s shown in PageSpeed Insights and Search Console. Many small sites don’t have enough visitors for it to appear at all.
  • Lab data comes from a single simulated visit, such as a Lighthouse test. It’s available for any page, it’s repeatable, and it shows why a page is slow, so it’s the one to work with.

A lab test can’t measure INP, because nobody actually taps anything. It reports Total Blocking Time (TBT) instead: how long the page keeps the phone’s processor too busy to respond. Under 200 ms is good; a high TBT almost always means a poor INP for real visitors.

What the overall score means

Lighthouse also rolls everything into a performance score from 0 to 100:

  • 90–100: good. Don’t spend money chasing the last few points.
  • 50–89: needs work. Usually there are one or two large, fixable causes.
  • Under 50: poor, and very likely costing you visitors.

The score moves a few points between runs, so look at the band, not the exact number. And remember it’s a summary: the three Core Web Vitals above are what actually describe the visitor’s experience.

How to test your own site in five minutes

  1. Run a mobile test of your homepage with our free website speed test. It simulates a mid-range phone and shows the main timings in plain language. Google’s PageSpeed Insights gives the same kind of test in more technical detail, plus field data if your site has enough visitors.
  2. Test your most important pages too, not only the homepage: the page your adverts link to, your main service page, your contact or booking page.
  3. Run each test twice and use the better result. The first run sometimes catches a cold cache.
  4. Check the real thing on your own phone. Turn off Wi-Fi, open the site in a private tab and count the seconds until you can read the main text and tap the menu.
  5. Write the numbers down, so you can see whether the next change made things better or worse.

What “too heavy” looks like in practice

There’s no official limit on page size, but every byte has to travel over a mobile connection before the page appears. Recently we tested an online shop whose product page weighed 26 MB on mobile. Most of it was one high-resolution video that started loading automatically, and the main product image appeared after about 30 seconds in the simulated phone test. Nothing was broken; the page was simply asking every visitor’s phone to download far too much.

That’s typical: a slow page usually has one or two big causes, not fifty small ones. Oversized images and videos, a pile of plugins, third-party widgets and slow hosting cover most cases. Our guide to why websites are slow on mobile goes through each one and the fixes in order.

Realistic targets for a small business site

  • Homepage and key pages: all three Core Web Vitals in the “good” band on a mobile test, and a Lighthouse performance score of 90 or more.
  • Pages with heavy features such as maps, booking widgets or video: LCP and CLS still good, with the heavy part loading only when the visitor asks for it.
  • After every change: retest. Sites rarely get slow in one go; they get slow one widget at a time.

How B63 helps

Speed is built in rather than added later. We build custom sites by default: every page is generated in advance as finished HTML, without a database or plugins running when a visitor arrives, and our own sites built this way score 98–100 on mobile in Google’s Lighthouse test. On our monthly plan (€0 upfront, then €150 per month excl. VAT for 24 months), keeping the site fast is part of the ongoing work, together with hosting, updates, backups and changes. More on our SEO and page speed page.

FAQ

Is 3 seconds fast enough?

For the main content of the page, Google’s “good” line is 2.5 seconds on a phone. A site at 3 seconds is close, and usually one fix away from passing.

Does speed affect Google rankings?

Core Web Vitals are one of many signals Google uses. Relevant, useful content matters more, but a slow page loses visitors before they read that content, so speed affects results either way.

Why is my score different every time I test?

Lab tests depend on network and server conditions at that moment, so a few points of variation is normal. Look at the band (good, needs work, poor) and at the three Core Web Vitals, not the exact score.

My site has no field data in PageSpeed Insights. Is something wrong?

No. Google only shows field data when enough real Chrome users have visited the page. Use the lab results until then; they show the same problems.

Want to know where your site stands? Run the free website speed test, or send us the address and we’ll tell you what we’d fix first.

Let's get your business found

Tell us a little about your business. We'll reply with a clear proposal for your website and everything around it, with no obligation.

Free proposal