Ask five different sources how fast a website should load and you'll get five different answers, ranging from "under 2 seconds" to specific millisecond thresholds for individual technical metrics.
"Load time" isn't one single measurement — it's a sequence of stages, each with its own benchmark.
The Simple Answer First
- Desktop Target: Under 2.0 seconds
- Mobile Target: Under 3.0 seconds
- Current Web Averages: 2.5 seconds on desktop, 8.6 seconds on mobile
Roughly 53% of mobile visitors abandon pages taking longer than 3 seconds to load (read how website speed impacts revenue).
The Benchmarks That Actually Matter
| Metric | What it measures | Good threshold |
|---|---|---|
| TTFB (Time to First Byte) | Server response speed | Under 0.8 seconds |
| LCP (Largest Contentful Paint) | Main visible content render | Under 2.5 seconds |
| INP (Interaction to Next Paint) | Tap/click response speed | Under 200 milliseconds |
| CLS (Cumulative Layout Shift) | Visual page stability | Under 0.1 |
| Mobile PageSpeed Score | Composite lab score | 90–100 |
TTFB precedes everything else. Sites with poor LCP spend an average of 2.27 seconds on TTFB alone — nearly exhausting the entire 2.5-second LCP budget before the browser even renders HTML.
Understanding TTFB (Time to First Byte)
Google's guidance specifies a good TTFB as 0.8 seconds or less (anything over 1.8 seconds is "poor"). While TTFB isn't a standalone Core Web Vital, a slow TTFB makes achieving a passing LCP score nearly impossible.
Lab Data vs. Real-World Field Data
- Lab Data (PageSpeed Insights): Simulated test in a controlled environment. Used for debugging.
- Field Data (Chrome UX Report / CrUX): Sourced from actual real-world visitors over a 28-day window. This is what Google uses to evaluate rankings.
Quick Stats
| Data point | Figure |
|---|---|
| Industry target load time | Under 2 seconds |
| Average desktop load time | 2.5 seconds |
| Average mobile load time | 8.6 seconds |
| Mobile abandonment threshold | 3+ seconds (53% leave) |
| Good TTFB | Under 0.8 seconds |
| Good LCP | Under 2.5 seconds |
| Good INP | Under 200 milliseconds |
| Good CLS | Under 0.1 |
Decision Framework
| Your situation | What it likely means |
|---|---|
| TTFB over 1.8 seconds | Hosting/server response issue — upgrade host or add caching |
| TTFB good, LCP over 2.5s | Front-end issue — compress images, remove render-blocking scripts |
| LCP fine, INP failing | Main-thread JavaScript execution issue |
| Consistently failing across all metrics | Site needs a structural rebuild rather than incremental patches |
Brandywebs builds custom high-performance websites starting from $999, engineered to pass speed benchmarks from day one (read custom website cost breakdown).
Get a free quote from Brandywebs →
FAQs
What is a good website load time in 2026? Under 2 seconds on desktop and under 3 seconds on mobile is the realistic target.
What is TTFB and why does it matter? Time to First Byte measures server response time before content rendering begins. Good TTFB is under 0.8 seconds.
Why does PageSpeed Insights score change between tests? Lab scores fluctuate based on instantaneous server load and network connection. Field data from real Chrome users is stable and used for ranking.
Is mobile or desktop load time more important? Mobile, since mobile traffic accounts for over 62% of all web visits and mobile load times average 3x slower than desktop.