Five Fast Fixes for a Better Page Speed Score
Page speed is one of the few ranking inputs you control completely. It will not lift a weak page above a strong one on its own, but a slow page loses visitors before they read a word, and Google's Core Web Vitals give it a measurable way to notice.
The good news is that most slow business websites share the same handful of problems. You rarely need a rebuild. You need to fix the few things that carry most of the weight, in the right order.
Below are five fixes that usually move a PageSpeed Insights score within a day or two, what each one improves, and how to check the result with field data rather than guesswork.
Key takeaways
- Images are usually the biggest single cause of a slow Largest Contentful Paint.
- Unused and render-blocking JavaScript harms both loading and responsiveness.
- Every third-party script — chat widgets, trackers, embeds — has a speed cost.
- Self-hosted, preloaded fonts with font-display: swap prevent invisible text and layout shift.
- Caching and a CDN cut server response time for repeat and distant visitors.
- Judge success by Search Console's Core Web Vitals field data, not a single lab score.
Why does page speed matter for SEO?
Google uses Core Web Vitals as part of its page experience signals. They measure what a visitor actually feels: how quickly the main content appears, how fast the page responds to a tap, and whether the layout jumps around while loading.
| Metric | What it measures | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | Time until the main content is visible | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds to input | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout moves unexpectedly | 0.1 or less |
Speed is a tie-breaker rather than a trump card. Where two pages answer a query equally well, the faster one has the edge — and it converts more of the visitors it earns. For the wider case, see why technical SEO is important.
1. How do you optimise images for speed?
On most small business sites the hero image is the Largest Contentful Paint element, and it is often a multi-megabyte photo straight from a camera or stock library.
- Resize images to the largest size they are actually displayed at.
- Convert to WebP or AVIF, which are typically far smaller than JPEG or PNG at the same quality.
- Use responsive
srcsetso phones download smaller files. - Lazy-load images below the fold, but never the hero image.
- Set width and height attributes so the browser reserves space and avoids layout shift.
This single fix frequently produces the largest score change of the five.
2. How do you reduce unused JavaScript?
JavaScript is the most expensive resource on the web: it must be downloaded, parsed and executed, and while the browser is busy it cannot respond to taps. That is why heavy scripts damage INP as well as loading.
- Remove plugins and libraries that no longer do anything visible.
- Add
deferorasyncto scripts that are not needed for the first render. - Split large bundles so each page only loads what it uses.
- Use the Coverage panel in Chrome DevTools to find code that never runs.
3. Which third-party scripts should you cut?
Chat widgets, heatmaps, multiple analytics tags, social embeds and ad pixels each add requests to servers you do not control. Individually they seem harmless; together they are often the reason a site fails Core Web Vitals.
Audit every tag and ask whether anyone has used its data in the last three months. Load the survivors after the page becomes interactive, or only on the pages that need them. Replace embedded videos with a lightweight thumbnail that loads the player on click.
4. How should fonts be loaded?
Web fonts can delay text from appearing and cause layout shift when they swap in. The fix is quick:
- Use two font families at most, and only the weights you actually use.
- Serve WOFF2 files, ideally self-hosted.
- Preload the main font file used above the fold.
- Set
font-display: swapso text shows immediately in a fallback font.
5. How do caching and a CDN help?
Before anything renders, the browser waits for your server to respond — Time to First Byte. Slow shared hosting, uncached database queries and distant servers all add delay.
- Enable page caching so pages are served ready-made.
- Set long cache lifetimes for static files such as images, CSS and fonts.
- Use a content delivery network so files come from a server near the visitor.
- Enable Brotli or gzip compression at the server or CDN level.
For businesses that rely on nearby customers, this matters most on mobile networks, where every round trip is felt. If you would rather have this handled alongside the rest of your search work, our SEO agency services include speed fixes as standard.
How do you measure whether the fixes worked?
PageSpeed Insights shows two kinds of data. The lab score is a single simulated test; field data comes from real Chrome users over the previous 28 days. Google ranks on field data.
| Lab data | Field data | |
|---|---|---|
| Source | Simulated test | Real visitors (CrUX) |
| Updates | Instantly | Rolling 28 days |
| Best for | Diagnosing issues | Judging ranking impact |
Check the Core Web Vitals report in Search Console four weeks after changes. A full technical SEO audit will find the deeper issues these quick wins do not cover.
Does page speed affect AI search visibility?
AI Overviews draw on pages Google has already crawled and indexed, and answer engines such as ChatGPT search and Perplexity fetch pages in real time. Slow, script-heavy pages can time out or render incompletely for those crawlers, which means your content may simply not be read.
Fast, server-rendered HTML with the answer in the page source is the safest format for being quoted by AI assistants.
Page speed glossary
- Core Web Vitals: Google's three user-experience metrics — LCP, INP and CLS.
- TTFB: Time to First Byte, how long the server takes to respond.
- Render-blocking resource: a file the browser must load before showing the page.
- Lazy loading: delaying off-screen images until the visitor scrolls to them.
- CDN: a network of servers that delivers files from a location near the visitor.
- CrUX: the Chrome User Experience Report, the source of field data.
Frequently asked questions
What is a good PageSpeed Insights score?+
90 or above is rated good, 50 to 89 needs improvement. More important than the score is passing all three Core Web Vitals in field data.
Is page speed a major ranking factor?+
It is a confirmed but modest signal. Relevance and quality matter more, but speed separates close competitors and improves conversions.
Why is my mobile score lower than desktop?+
Mobile tests simulate a slower device and network, so heavy images and JavaScript hurt far more. Optimise for mobile first.
How long until speed improvements show in Search Console?+
Field data covers a rolling 28 days, so allow about four weeks for the Core Web Vitals report to reflect changes.
Do I need a new website to improve speed?+
Rarely. Image, script, font and caching fixes resolve most problems on existing sites.
Do WordPress plugins slow sites down?+
Many do, especially page builders and plugins that load scripts sitewide. Remove unused ones and use a caching plugin.
Fix the heavy things first
Speed work rewards order. Start with images, then JavaScript and third-party scripts, then fonts and caching. Those five fixes solve the majority of slow business sites without a rebuild.
Measure with field data, give it a month, and treat speed as part of ongoing technical health rather than a one-off project.
Related reading
Why is technical SEO important?
Technical faults quietly cap the return on every other marketing pound. The commercial case, with the failure patterns that cost most.
What is a technical SEO audit?
A real audit narrows hundreds of observations to the few problems costing you money. What to expect, and how to judge one.
Technical SEO vs on-page SEO
Why technical foundations and on-page relevance both matter, and how to prioritise.