There is no shortage of opinions about how fast a website should load. You will find articles claiming 2 seconds, 3 seconds, or even 1 second as the target. The honest answer is that it depends on what you are measuring and who you are measuring it for.
This guide covers the benchmarks that actually matter in 2026, what Google considers fast, and how to work out whether your site is fast enough. If you want to check your numbers first, run our instant speed test to get your current scores.
The benchmarks that matter
There are several ways to measure website speed. The ones that matter most in 2026 are the Core Web Vitals, because these are the metrics Google uses for ranking and they reflect real user experience.
| Metric | What It Measures | Good | Needs Improvement | Poor |
|---|---|---|---|---|
| LCP | Loading speed | Under 2.5s | 2.5s to 4s | Over 4s |
| INP | Responsiveness | Under 200ms | 200ms to 500ms | Over 500ms |
| CLS | Visual stability | Under 0.1 | 0.1 to 0.25 | Over 0.25 |
If your site meets all three “good” thresholds for the majority of your visitors, Google considers your site fast. That is the benchmark that matters for search rankings.
What about total page load time?
Total page load time (the time until everything on the page has finished loading) is less important than it used to be. Modern browsers render content progressively, so users can see and interact with your page long before every image, script, and font file has finished downloading.
That said, total load time still affects perception. As a general guide:
| Load Time | User Perception |
|---|---|
| Under 1 second | Feels instant. Users do not notice any delay. |
| 1 to 2 seconds | Feels fast. Most users are satisfied. |
| 2 to 3 seconds | Feels acceptable. Some users start to notice. |
| 3 to 5 seconds | Feels slow. You are losing a measurable percentage of visitors. |
| Over 5 seconds | Feels broken. More than half of mobile visitors may leave before the page finishes loading. |
Google research published in 2017 found that as page load time increased from 1 to 3 seconds, the probability of a visitor leaving increased by 32%. From 1 to 5 seconds, the probability increased by 90%. These findings have been reinforced by more recent studies from Deloitte, Portent, and Akamai.
How fast is the average website?
The average website is slower than most people assume. According to data from the HTTP Archive (which tracks the performance of millions of websites), the median page load time on mobile in 2025 was approximately 8 to 9 seconds for full page load, with a median Largest Contentful Paint of around 4 seconds on mobile.
This means that if your site loads its main content in under 2.5 seconds on mobile (an LCP of 2.5 seconds or less), you are already faster than the majority of the web. You do not need to be the fastest site on the internet. You need to be fast enough that speed is not costing you visitors or rankings.
How do different platforms compare?
Platform matters. Some content management systems and website builders produce faster sites out of the box than others.
| Platform | Typical Mobile LCP | Notes |
|---|---|---|
| Static HTML / Jamstack | 1.0 to 2.0s | Fastest category. Pre-built pages served from CDN. |
| Managed WordPress (optimised) | 1.5 to 3.0s | With quality hosting, caching, and image optimisation. |
| Standard WordPress (unoptimised) | 3.5 to 7.0s | Typical small business site with a page builder and 20+ plugins. |
| Shopify | 2.0 to 4.0s | Theme-dependent. App bloat is the main variable. |
| WooCommerce | 3.0 to 6.0s | Heavier than standard WordPress due to ecommerce functionality. |
| Squarespace | 2.5 to 4.5s | Consistent but limited optimisation options. |
| Wix | 3.0 to 5.0s | Performance has improved but still platform-constrained. |
These are typical ranges, not guaranteed outcomes. An optimised WordPress site can outperform a poorly configured static site, and a lean Shopify store can be faster than a bloated Squarespace site. The platform sets the baseline; optimisation determines the outcome.
If you run WordPress and your LCP is above 3 seconds, see our guide on how to speed up WordPress. For WooCommerce or Shopify, our WooCommerce and Shopify service pages cover platform-specific fixes.
What Google considers fast
Google does not define “fast” with a single number. Instead, it uses the Core Web Vitals thresholds applied to real user data from Chrome browsers.
A page passes Core Web Vitals when at least 75% of its real visitors experience all three metrics in the “good” range. This is measured over a rolling 28-day period using the Chrome User Experience Report (CrUX).
In practice, this means:
- LCP under 2.5 seconds for 75% or more of visits
- INP under 200 milliseconds for 75% or more of visits
- CLS under 0.1 for 75% or more of visits
If your site meets these thresholds, Google classifies it as having good page experience. This is the standard that matters for SEO rankings.
You can check your site’s Core Web Vitals status in Google Search Console. For a quick check, our instant speed test shows your lab-based Core Web Vitals alongside your performance score.
How fast should your site be?
The right target depends on what your website does and who visits it.
Brochure and service sites (like most small business websites): Aim for an LCP under 2.5 seconds on mobile and a PageSpeed score above 70. Your visitors are forming a first impression. A slow site undermines trust before they have read a word.
Ecommerce sites: Aim for an LCP under 3 seconds on mobile across all key pages (homepage, category, product, checkout). Deloitte research found that a 0.1-second improvement in mobile load time increased conversion rates by 8.4% for retail sites and increased average order value by 9.2%.
Content and blog sites: Aim for an LCP under 2.5 seconds. Readers will wait slightly longer for in-depth content, but a slow initial load still increases bounce rate. The first 3 seconds determine whether someone stays to read or hits the back button.
Web applications: INP matters more here than LCP. Users expect responsive interactions. Aim for INP under 200 milliseconds across all key workflows.
What to do if your site is too slow
If your site does not meet the benchmarks above, the good news is that speed is one of the most fixable aspects of a website. Here is where to start:
-
Run a speed test. Use our instant speed test to see your current scores and Core Web Vitals. Note which metrics are in the red or amber range.
-
Identify the biggest issues. PageSpeed Insights provides a prioritised list of opportunities with estimated time savings. Focus on the items at the top of the list.
-
Fix the fundamentals first. Image optimisation, caching, and removing unnecessary scripts solve the majority of speed problems. See our guide on why websites are slow for a breakdown of the most common causes.
-
Check your Core Web Vitals. If individual metrics are failing, our guide on how to improve Core Web Vitals covers specific fixes for LCP, INP, and CLS.
-
Get professional help if needed. If you would rather hand the problem to someone else, request a free speed check from us. We run a full manual audit and send you a clear report showing exactly what needs fixing and what it will cost.
The bottom line
In 2026, a website that loads its main content in under 2.5 seconds on mobile, responds to interactions in under 200 milliseconds, and does not shift content around while loading is considered fast by Google and by users. That is the standard to aim for.
Most small business websites do not meet this standard, which means improving your speed gives you a genuine competitive advantage. You do not need a perfect score. You need to be fast enough that speed is working for you rather than against you.
If your site is not there yet, our website speed optimisation service handles the diagnosis, the fixes, and the measurement so you can see the difference in real numbers.
Frequently asked questions
Is a 3-second load time good enough? For total page load, 3 seconds is acceptable for most sites. But total load time is less important than Largest Contentful Paint (LCP), which Google measures. An LCP under 2.5 seconds on mobile is the threshold for “good.” If your LCP is under 2.5 seconds but total load is 3 to 4 seconds, you are probably fine.
Why is my mobile speed so much worse than desktop? Mobile speed tests simulate a mid-range phone on a throttled 4G connection. Desktop tests simulate a fast computer on broadband. Most real mobile visitors are on slower connections than desktop visitors, which is why Google prioritises mobile performance for ranking purposes.
Does my site need to load in under 1 second? No. Sub-1-second load times are excellent but not necessary for good user experience or SEO. A site with an LCP of 1.8 seconds and good Core Web Vitals is performing well. Focus on meeting the Core Web Vitals thresholds rather than chasing an arbitrary total load time.
How often should I test my site speed? Test after any significant change (new plugin, theme update, content addition). Beyond that, monthly checks are sufficient for most sites. If you want ongoing monitoring without doing it yourself, our maintenance plans include monthly performance checks with regression alerts.
My speed test scores are different every time. Which one is right? Speed test scores vary between runs because of server load, network conditions, and the simulated environment. Run the test 3 times and take the median result. For the most reliable picture, use field data from Google Search Console rather than lab test scores.
Want us to check your site speed?
Get a free, no-obligation speed report for your website. We will tell you exactly what is slowing it down and what to do about it.