What Is a Good PageSpeed Score in 2026?

Every website owner eventually asks the same question: "Is my PageSpeed score good enough?" It's a fair question, but the answer isn't as simple as a single number. A score of 72 on mobile might be excellent for a content-heavy e-commerce site, and terrible for a simple landing page. Context matters more than most people realize.

Let's cut through the confusion. This article explains exactly how PageSpeed scores work in 2026, what ranges you should target, and — perhaps most importantly — when to stop obsessing over the number and focus on what actually impacts your users and rankings.

How PageSpeed Scores Are Calculated

Google's PageSpeed Insights uses Lighthouse to generate a performance score from 0 to 100. The score combines five lab metrics, not an assessment of every real visitor. For the underlying technology read what PageSpeed Insights does; for actual score weights and First Fix selection see the SnapSiteScan methodology.

The five metrics and their current weights are: First Contentful Paint (10%), Largest Contentful Paint (25%), Total Blocking Time (30%), Cumulative Layout Shift (25%), Speed Index (10%). These weights can change as Lighthouse evolves; inspect the version used by your report.

Lighthouse maps each metric to a scoring curve and combines the resulting scores. The result is not your current percentile against every website or a ranking forecast.

The Score Ranges: What They Mean

Google divides scores into three color-coded categories. Green (90–100) means your page performs well. Orange (50–89) means there's room for improvement. Red (0–49) means your page has significant performance issues.

But here's the nuance most articles won't tell you: a "good" score depends entirely on your type of site. A static blog or portfolio site should absolutely aim for 90+. A complex web application with dynamic content, authentication, and third-party integrations will struggle to break 70 on mobile — and that might be perfectly acceptable.

Use lab scores for diagnosis and check Core Web Vitals field observations separately. URL and origin CrUX data are not interchangeable, and one Lighthouse run cannot establish a field pass. Neither a higher lab score nor passing field metrics guarantees that one page will outrank another; relevance and other signals still matter.

Illustrative screenshots · not a verified current Stripe measurement

What a 72 actually looks like

These retained screenshots illustrate the report layout. Their capture conditions and measurement date are not established here, so 72 is not a verified current Stripe performance result.

What this tells you

Website Health combines four categories; it is not a mobile Performance score. Use the measured values and findings from your own scan, not these example numbers.

Why Mobile Scores Are Always Lower

If you've ever tested your site and seen a desktop score of 95 but a mobile score of 55, you're not alone. This is completely normal and happens because Lighthouse simulates a mid-range phone on a throttled 4G connection for mobile tests. Desktop tests assume a powerful computer on a fast connection.

The gap matters because Google uses mobile-first indexing. Your mobile score is what influences rankings, not your desktop score. This is why optimizing for mobile performance should always be your priority. Our guide on mobile vs desktop performance explains the differences in detail and how to close the gap.

For mobile, aim for 70+ as a realistic baseline. Getting above 80 puts you ahead of most competitors. Above 90 on mobile with real content is genuinely impressive and usually requires careful optimization of every asset on the page.

Does a Perfect 100 Matter?

Short answer: no. A score of 100 means you've optimized every lab metric to perfection, but it doesn't guarantee better rankings or more conversions than a score of 92. The difference between 90 and 100 is almost always insignificant in terms of actual user experience.

Chasing a perfect score can actually be counterproductive. You might remove useful analytics tools, strip out interactive features, or spend days shaving off milliseconds that no user will ever notice. That time is almost always better spent on content, UX, or addressing actual SEO issues that prevent indexing.

The sweet spot for most websites is between 85 and 95 on desktop, and 65 and 85 on mobile. If you're in that range with passing Core Web Vitals, your performance is not holding you back.

One number hides four different problems

The overall Website Health score is a rollup. The four Lighthouse categories underneath tell you which kind of problem you have — and they usually don't move together. This separate illustrative category screenshot is not evidence of the same scan as the 72 above:

Performance 92 · Good

Loads and renders quickly on the tested device.

SEO 78 · Needs work

Missing crawlability signals — often meta tags or link-text quality.

Accessibility 95 · Good

Contrast, labels, and ARIA are mostly in order.

Best Practices 83 · OK

A few flagged console errors or deprecated APIs.

These illustrative values 92, 78, 95 and 83 produce Website Health 88 with our weights, not 72. Do not combine separate screenshots into one result. Review actual category scores and findings from your own scan.

How to Improve Your Score

If your score is lower than you'd like, start with the highest-impact optimizations. These typically give you the biggest score jumps with the least effort.

Optimize images. This is the single most common reason for poor scores. Convert images to WebP or AVIF format, resize them to the dimensions they're actually displayed at, and add lazy loading to images below the fold. The impact depends on your page and test conditions; rescan to measure it rather than assuming a point gain.

Reduce JavaScript. Total Blocking Time has the highest weight in the score calculation (30%). Every kilobyte of JavaScript your page loads has to be parsed, compiled, and executed. Remove unused libraries, defer non-critical scripts, and consider whether you really need that chat widget loading on every page.

Fix server response time. If your Time to First Byte (TTFB) is slow, everything else is delayed. A fast server and proper caching strategy lay the foundation for good performance. Our article on server response time explains why TTFB matters and how to improve it.

For a comprehensive list of speed improvements, check our guide on how to make your website faster. And if you want to prevent performance regression after improving, consider setting up performance budgets.

What Score Should You Actually Aim For?

Here's a practical framework based on site type:

Static sites and blogs: 90+ mobile, 95+ desktop. These are lightweight by nature, so there's no excuse for a poor score. If you're below 90, something is wrong — usually unoptimized images or unnecessary JavaScript.

Business and marketing sites: 75+ mobile, 90+ desktop. Third-party tools (analytics, chat widgets, CRM integrations) will always drag your mobile score down. Focus on keeping Core Web Vitals green.

E-commerce and web apps: 60+ mobile, 80+ desktop. Dynamic content and complex functionality make high scores harder. Prioritize real-user metrics over lab scores.

Regardless of your site type, run a scan with SnapSiteScan to see where you stand. The report breaks down exactly which metrics are pulling your score down and suggests specific fixes — sorted by impact so you know where to start.

The Bottom Line

A good PageSpeed score in 2026 isn't a specific number — it's a range that matches your site's complexity. Focus on passing Core Web Vitals with real-user data, aim for green on desktop and high orange on mobile, and spend your optimization time on changes that users will actually feel. The score is a compass, not a destination.