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 is not the goal — passing Core Web Vitals and outperforming your competitors is. Google's own Lighthouse documentation calls a perfect score "extremely challenging to achieve and not expected", and treats anything from 90 up as good. Sacrificing useful features to squeeze out a few more points 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. Google itself says that "trying to get a perfect score just for SEO reasons may not be the best use of your time." The goal is:

Pass all three Core Web Vitals (the Core Web Vitals assessment in PageSpeed Insights)
Be fast enough that visitors do not notice lag
Outperform your direct competitors

What a realistic score looks like

Google uses three bands, not four, and colours them:

Score	Google's label	What it usually means in practice
90–100 (green)	Good	A lean, well-optimized site. Often a simpler site, or one with very careful optimization.
50–89 (orange)	Needs improvement	Where most real business sites sit. The high end of this band is genuinely fine; the low end is worth work.
0–49 (red)	Poor	Visitors are likely noticing the slowness. Significant work needed.

That middle band is wide, so the number alone does not tell you much: an 85 and a 55 are both "needs improvement" and they are nothing like the same site. Look at the individual measurements underneath, not just the headline.

Note also that the score is calculated on a curve. Google's documentation says taking a score from 99 to 100 needs roughly as much improvement as taking it from 90 to 94 — the last few points cost far more than the first ones.

A score of 78 with all Core Web Vitals passing is a better place to be than a score of 95 with a failing CLS.

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 — the weighting of each measurement has been revised more than once
Between test runs, for reasons that have nothing to do with your site

That last one catches people out. Google's own list of causes includes ads or A/B tests serving different content, internet routing changes, testing on a different device, browser extensions injecting scripts, and antivirus software. Google suggests thinking of your site's performance as a spread of scores rather than one number.

So do not obsess over a single reading. Watch for trends — if your score drops and stays down after a change, investigate that change.

What "passing" Core Web Vitals means in practice

Core Web Vitals are the targets worth caring about, and Google confirms its ranking systems use them. The "good" thresholds are:

LCP — 2.5 seconds or less: your main content loads quickly
INP — 200 milliseconds or less: the page responds to taps and clicks immediately
CLS — 0.1 or less: the layout stays stable as it loads

Hitting the number exactly still counts as good. "Passing" has a precise meaning in PageSpeed Insights: your page passes the Core Web Vitals assessment when the 75th percentile of real visitors is in the good band for all three. If there is not enough visitor data for INP, LCP and CLS alone decide it; if LCP or CLS is thin, the page cannot be assessed at all.

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 a cached copy can outlive the edit that should have replaced it. Most caching plugins clear the cache when you update a page; a CDN or a server-level cache in front of it may not, so a flash sale can lag behind you.

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

A developer told me they could get my site to 100/100. Should I trust that?

Be cautious. Achieving 100/100 on a real business website often requires removing useful features or aggressively caching content in ways that can cause stale data problems. Some developers run the test on a stripped-down version of the site, or under conditions that do not reflect real visitor experience. Ask what they would need to change to achieve it, and make sure the tradeoffs are acceptable.

How often should I worry about my performance score?

Check it after major changes (a redesign, adding a new plugin, a content refresh) and every three to six months as routine maintenance. Outside of that, focus on running a good business — not obsessing over numbers.

My competitor has a worse score but ranks higher. Why?

Search ranking depends on many signals, and there is no single "page experience" score that decides it. Google's own answer is that Search "always seeks to show the most relevant content, even if the page experience is sub-par" — page experience contributes most when there is a lot of equally helpful content competing for the same query. So a competitor with a slower site but content that answers the question better can still outrank you. Speed is a real factor; it is not a trump card.

Need a hand?

If you're stuck, email support@chykalophia.com and we'll help. Include your website address and a screenshot if you can.