Performance: realistic expectations
What a good performance score actually looks like, why perfect scores are not always possible or necessary, and how to set realistic goals.
It is easy to become fixated on achieving a perfect 100/100 score in Google PageSpeed Insights. But that goal can be misleading — and chasing it can lead to sacrificing things your business actually needs. This guide explains what good performance really looks like in the real world.
Quick summary
A perfect 100 score is not the goal — passing Core Web Vitals and outperforming your competitors is. Many excellent, fast websites score in the 70s or 80s. Sacrificing useful features to squeeze out a higher score is rarely worth it.
Why perfect scores are rare (and not the goal)
Many features that make a website functional and engaging affect performance scores:
- A live chat widget is useful for customers — but it adds external scripts
- Google Analytics is essential for measuring your business — but it is a third-party script
- A well-designed hero image makes a strong first impression — but large images cost something
- A contact form, a cookie consent banner, social media embeds — all real, valuable features
A site that has none of these things and is entirely static text might score 100/100. A real business website with real features will score lower. That is normal and expected.
The goal is not perfection. The goal is:
- Pass all three Core Web Vitals (green status in PageSpeed Insights)
- Be fast enough that visitors do not notice lag
- Outperform your direct competitors
What a realistic score looks like
| Score | What it usually means |
|---|---|
| 90–100 | Excellent. A lean, well-optimized site. Often a simpler site or a site with very careful optimization. |
| 75–89 | Good. A real business site with good optimization. Most visitors experience it as fast. |
| 50–74 | Needs improvement. There are meaningful optimizations to make. Worth investigating. |
| Below 50 | Poor. Visitors are likely noticing the slowness. Significant work needed. |
A score of 78 with all Core Web Vitals green is a better situation than a score of 95 with a red CLS score.
Scores are not static
Your score is a snapshot. It changes:
- When you add new plugins or scripts
- When images are uploaded without optimization
- When a new version of a plugin loads more code
- When Google changes how it scores (PageSpeed's scoring methodology evolves)
- Between test runs, due to server load and network variability
Do not obsess over a single number. Watch for trends — if your score drops significantly after a change, investigate that change.
What "passing" Core Web Vitals means in practice
Google's Core Web Vitals are the most meaningful performance targets because Google uses them for ranking. The green thresholds are:
- LCP under 2.5 seconds — your main content loads quickly
- INP under 200 milliseconds — the page responds to interactions immediately
- CLS under 0.1 — the layout stays stable as it loads
Most visitors would describe a site hitting these thresholds as "fast." They would not think about it at all — which is the real goal.
Comparing to your competitors
A useful question is not "what is my score?" but "is my site faster than my competitor's?" If your competitor's site is a 55 and yours is a 70, you are winning on speed — regardless of either number being far from 100.
You can test a competitor's site with the same tools you use to test your own.
The tradeoffs are real
Some performance optimizations come with genuine costs:
Aggressive caching makes pages faster — but means updates take longer to propagate. A flash sale might not appear immediately after you publish it.
Fewer fonts reduces load time — but may mean compromising your brand typography.
Removing third-party scripts improves speed — but might mean losing analytics, chat support, or conversion tracking.
Simplifying features reduces JavaScript — but might limit functionality your visitors rely on.
There is no right answer for every situation. Good performance work involves honest conversation about which tradeoffs make sense for your business — not blindly chasing a number.
Our approach
When we work on your site's performance, we focus on the changes with the biggest impact and fewest tradeoffs first — usually images, hosting, and caching. We discuss anything that affects your site's functionality before making changes.
Common questions
Related guides
- Core Web Vitals explained
- How to measure your site's speed
- Website performance checklist
- SEO: setting realistic expectations
Need a hand?
Learn more
Fonts & page speed
How web fonts affect your site's load time, why they can cause text to flash or jump, and how to minimize their impact on performance.
Website performance checklist
A practical checklist of the most important actions to keep your website fast — for both your team and your web developers.