A 90+ mobile PageSpeed score comes from four things: compressed modern-format images, removing third-party scripts you do not need, loading fonts without blocking render, and serving cached, compressed files. Fix those in that order and most sites clear 90 without a rebuild.
Why is my website slow?
In most cases, because of things bolted on after launch. Chat widgets, analytics tools, social embeds, tracking pixels, review widgets and a font library nobody chose deliberately.
Each one seemed harmless. Together they are the reason a site that scored 95 at launch scores 48 two years later.
The second most common cause is images — usually photographs uploaded at camera resolution and displayed at a fraction of their size.
What score should I actually aim for?
Aim for 90+ on mobile, measured on real hardware. Desktop scores flatter everyone and are close to meaningless as a target.
Be honest about the trade-off: chasing a perfect 100 usually means stripping functionality your business needs. The commercially sensible target is comfortably in the nineties on a mid-range phone over a normal connection. Test at PageSpeed Insights and pay attention to the field data, not just the lab score.
How do I fix images?
Images are usually the largest single win, and the easiest.
- Resize before uploading. A logo displayed at 40 pixels does not need to be 2000 pixels wide. This one mistake alone can add hundreds of kilobytes to every page.
- Use modern formats. WebP typically cuts file size substantially against JPEG and PNG at the same visual quality.
- Set width and height attributes. This reserves the space before the image loads and stops the page jumping around as it renders.
- Lazy-load below the fold — but never lazy-load your main hero image, which is usually the element the score is measuring.
Real example from this site: the logo was a 2000×2000 pixel file weighing 108KB, loaded twice on every page for light and dark themes. Replaced with a single transparent version at 4.6KB, inverted by CSS for dark mode. That removed roughly 217KB from every single pageview, with no visible difference.
Which scripts should I remove?
Third-party scripts are the silent killers of performance, because each one opens a connection to a server you do not control.
Audit them ruthlessly. For each one, ask a single question: what does this earn?
- A chat widget nobody uses costs you speed on every visit.
- Three analytics tools measuring the same thing is two too many.
- Social feed embeds are often the heaviest element on a page and the least clicked.
Removing what you do not need is faster, cheaper and more permanent than optimising around it.
How should fonts be loaded?
Fonts are the most common hidden bottleneck, because the mistake is invisible in the browser.
Never load fonts with @import inside your CSS file. The browser has to download the stylesheet, parse it, discover the font request, then open a fresh connection — a chain of round trips before anything appears.
Instead, use a <link> in the <head> with preconnect, add display=swap so text shows immediately in a fallback, and define a system font stack so nothing renders blank while the webfont arrives.
This site had exactly that @import problem. Moving to preconnect plus a proper link tag removed a serialised chain sitting directly in front of first paint.
What should the server be doing?
Three settings, usually in .htaccess on shared hosting:
- Compression. Gzip or Brotli on HTML, CSS, JavaScript and SVG. Typically cuts text transfer by around 70%.
- Cache headers. A long cache lifetime on images, CSS and fonts, so repeat visitors download almost nothing.
- HTTPS with HTTP/2 or better. Multiple files load in parallel rather than queueing.
These take minutes to configure and benefit every page permanently. They are the highest return-per-effort work in performance.
Does speed still affect rankings?
Yes, but indirectly and less than people claim. Speed will not lift a weak page above a strong one. It will lose you the visitor who arrived and left before anything appeared.
The stronger commercial argument is conversion, not ranking. Every second of delay costs you people who were already interested — and those are the most expensive visitors you have, because you paid to get them.
How do I keep the score after launch?
Scores decay. Someone adds a widget, uploads an unresized photo, installs a plugin, and six months later you are back at fifty.
- Test monthly and note the score, so decay is visible early.
- Set a rule that nothing gets added without checking its weight first.
- Resize images before upload, every time, without exception.
What to do this week
In order of return:
- Find your three largest images and resize them to the dimensions they actually display at.
- List every third-party script and delete the ones nobody can justify.
- Check how your fonts load. If you find
@importin your CSS, that is your bottleneck. - Turn on compression and cache headers if they are not already set.
Most sites clear 90 on those four alone — no rebuild required. If you would rather it were done properly and permanently, see how we approach website development, or read our guide to ranking on Google in 2026.
Frequently asked questions
Is a 100 PageSpeed score worth chasing?
Usually not. Getting from 90 to 100 often means removing functionality your business actually needs. Aim for comfortably above 90 on mobile and spend the remaining effort on conversion instead.
Does website speed affect Google rankings?
It is a ranking signal, but a modest one — speed will not lift a weak page above a strong one. The stronger argument is commercial: slow pages lose visitors you already paid to attract.
Should I use WebP images?
Yes for photographs and most graphics — it cuts file size substantially at the same visual quality and is supported by every current browser. Keep SVG for logos and icons, which stay sharp at any size.
Why is my site fast on desktop but slow on mobile?
Desktop tests run on more powerful hardware over better connections, which hides problems. Mobile is where JavaScript execution and image weight actually hurt, and it is what Google measures for indexing.
Will a faster host fix my slow website?
Rarely. Hosting matters, but most slow sites are slow because of page weight and third-party scripts. Moving heavy pages to a faster server makes heavy pages arrive slightly sooner.
Want this done properly?
We build and maintain this for businesses in 50+ countries. Tell us what you are working with and we will tell you straight what needs doing.
Start a conversation →