How Fast Should Your Website Load? Speed Benchmarks for 2026

The average website takes 2.5 seconds to load on desktop and 8.6 seconds on mobile. Google requires your Largest Contentful Paint under 2.5 seconds to pass Core Web Vitals. Users expect pages to load in under 2 seconds. There is a wide gap between what the web delivers and what both search engines and people demand, and website speed is the factor that closes it.

If you want a full SEO audit that includes speed signals, see our guide on how to test your website for SEO. For broader optimization, start with the SEO website guide.

Sources:

• Web Vitals (web.dev)
• HTTP Archive: Loading Speed Report
• Think with Google: Mobile Speed Benchmarks

What Google actually requires#

Google does not use a single "speed score." It measures three Core Web Vitals, and each has a hard threshold. Your page either passes or fails.

There is also a less-discussed threshold that matters: Time to First Byte (TTFB). While not an official Core Web Vital, Google's documentation identifies TTFB under 800ms as "good" and under 500ms as ideal. A slow TTFB makes it nearly impossible to hit a good LCP because the browser cannot start rendering until it receives data from the server.

Google uses the 75th percentile of all page loads to evaluate your CWV. That means 75% of your visitors need to have a "good" experience for the page to pass. If your audience skews mobile-heavy or is geographically far from your server, the 75th percentile will be worse than your own experience testing the page.

Sources:

• Web Vitals: Essential metrics for healthy sites
• Interaction to Next Paint (INP)
• Time to First Byte (TTFB)
• Core Web Vitals and Google Search

What users expect vs. what they get#

Users do not think in Core Web Vitals. They think in seconds. And their tolerance is shrinking.

47% of users expect a web page to load in 2 seconds or less. After 3 seconds, abandonment rates spike. By 5 seconds, the bounce rate approaches 38% compared to 9% for pages that load within 2 seconds.

Here is where the average website actually lands:

The desktop experience is tolerable for most users. The mobile experience is not. The 8.6-second average on mobile is over four times what users expect. This is not a minor usability issue. It is a structural problem that affects rankings, revenue, and user trust.

Every additional second of load time has a compounding cost. Research from Portent found that conversion rates drop by an average of 4.42% with each additional second of load time in the first five seconds. A site loading in 1 second converts at nearly 3x the rate of a site loading in 5 seconds.

Sources:

• Portent: Site Speed and Conversion Rates
• HTTP Archive: State of the Web
• Think with Google: Mobile Speed Benchmarks

Speed benchmarks by site type#

Not all websites have the same performance ceiling. A static blog and a SaaS dashboard are fundamentally different. Here are realistic benchmarks by category, based on HTTP Archive data and CrUX field measurements.

These benchmarks are targets, not pass/fail thresholds. But they give you a realistic standard to measure against sites of your type, rather than comparing a heavy web app to a static blog.

The biggest gap we see is in SaaS. Many SaaS landing pages load third-party analytics, chat widgets, A/B testing scripts, and marketing pixels that push LCP past 4 seconds on mobile. The irony: these scripts are meant to improve conversion, but they hurt conversion by slowing the page.

Sources:

• HTTP Archive: Loading Speed
• Chrome UX Report (CrUX)

Core Web Vitals pass rates by framework and CMS#

Not all technology stacks are created equal when it comes to speed. The Chrome UX Report tracks real-world CWV pass rates across origins (websites) by technology.

The key takeaway: your framework sets a floor, but your implementation determines where you land. A well-optimized WordPress site can outperform a poorly configured Next.js app. A Shopify store with a bloated theme can be slower than a lean WordPress site.

Sources:

• Chrome UX Report
• HTTP Archive: CWV by Technology

Speed optimization priority list (ordered by impact)#

Not all optimizations deliver equal results. Here is a priority list ordered by typical impact, based on the most common issues we see across hundreds of sites.

For a broader SEO optimization plan that includes speed alongside content and links, see 10 quick SEO fixes.

Sources:

• Optimize Largest Contentful Paint
• Eliminate render-blocking resources
• Reduce JavaScript payloads with code splitting

The mobile speed gap#

The gap between desktop and mobile performance is the single biggest blind spot in website speed optimization. Most developers test on fast laptops with wired connections. Their users are on 3-year-old phones with spotty 4G.

Desktop average: 2.5 seconds. Mobile average: 8.6 seconds. That is a 3.4x difference.

The reasons are structural:

• CPU power: A mid-range Android phone has roughly 4-6x less processing power than a modern laptop. JavaScript that parses in 200ms on your MacBook takes over a second on a Galaxy A14.
• Network latency: 4G connections add 50-100ms of latency per request. On 3G (still common globally), that jumps to 200-400ms.
• Memory constraints: Mobile browsers aggressively garbage-collect, causing jank and re-renders that do not happen on desktop.
• Thermal throttling: After a few seconds of heavy JavaScript execution, mobile CPUs throttle to prevent overheating, making the problem worse over time.

How to test mobile performance accurately:

• Use PageSpeed Insights (uses real mobile field data from CrUX)
• In Chrome DevTools, enable CPU throttling (4x slowdown) and network throttling (Slow 4G)
• Test on an actual mid-range Android device, not just an iPhone
• Check your Google Search Console Core Web Vitals report filtered by mobile

For mobile-heavy audiences (most B2C sites), optimizing mobile speed should be the primary focus, not an afterthought.

Sources:

• Statista: Mobile share of global web traffic
• HTTP Archive: First Contentful Paint by device

The cost (and ROI) of speed optimization#

Nobody talks about what speed optimization actually costs. Here is a realistic breakdown.

The first four items on this list are free and can be done in a single day. Together they typically deliver a 1-3 second improvement, which is enough to move most sites from "poor" to "good" on Core Web Vitals.

The ROI math is straightforward. If your site generates $10,000/month in revenue and a 1-second speed improvement lifts conversions by 7%, that is $700/month in additional revenue. A free afternoon of image optimization and CDN setup pays for itself immediately.

For startups watching costs, see our startup SEO guide which covers how to prioritize speed alongside other SEO fundamentals when resources are limited.

Sources:

• Portent: Site Speed and Revenue
• The business impact of Core Web Vitals

10-minute speed audit anyone can run#

You do not need expensive tools or technical expertise. Here is a complete speed audit using three free tools that takes 10 minutes.

For a complete SEO audit beyond speed, see our full SEO testing checklist.

FAQs#

How fast should a website load in 2026?#

Under 2.5 seconds for Largest Contentful Paint (LCP) to pass Google's Core Web Vitals. Under 2 seconds to meet user expectations. The best-performing sites load in under 1.5 seconds on desktop and under 2.5 seconds on mobile. Aim for the "good" threshold on all three CWV: LCP under 2.5s, INP under 200ms, and CLS under 0.1.

Does website speed affect SEO rankings?#

Yes. Core Web Vitals are a confirmed Google ranking signal. Sites that pass all three CWV have a measurable ranking advantage, particularly on mobile. Speed is not the strongest ranking factor (content relevance and backlinks still dominate), but when two pages are otherwise equal, the faster one ranks higher. For more on ranking factors, see our website rank guide.

What is a good PageSpeed Insights score?#

A score of 90-100 is "Good," 50-89 is "Needs Improvement," and below 50 is "Poor." But the score matters less than the individual Core Web Vitals metrics. A site can score 85 but still pass all CWV in field data. Focus on the green/amber/red indicators for LCP, INP, and CLS rather than obsessing over the overall number.

Why is my website so slow on mobile?#

The most common causes: uncompressed images, too many JavaScript files loading at once, no CDN (so mobile users far from your server experience high latency), render-blocking CSS in the head, and third-party scripts (analytics, chat widgets, ad trackers). Mobile devices also have less CPU power and higher network latency than desktops, amplifying every issue.

How much does 1 second of load time cost in revenue?#

Studies consistently show a 1-second delay reduces conversions by 4-7%. For an e-commerce site doing $100,000/month, that is $4,000-7,000/month lost to a single second of delay. Even for lead-generation sites, slower pages produce fewer form submissions and higher bounce rates. The ROI on speed optimization is almost always positive.

Should I optimize for desktop or mobile speed first?#

Mobile. Over 63% of global web traffic comes from mobile devices, and Google uses mobile-first indexing. If your mobile speed is poor, your rankings suffer regardless of how fast your desktop experience is. Most speed improvements (image optimization, CDN, lazy loading) benefit both, but always test and prioritize the mobile experience.

How often should I check my website speed?#

Monthly at minimum. Check Google Search Console's Core Web Vitals report for field data trends. Run PageSpeed Insights after any major deploy (new features, theme changes, plugin additions). Set up monitoring with a tool like SpeedCurve or just add a monthly calendar reminder to run the SEO checker and PageSpeed Insights on your top 5 pages.