A slow website costs you twice. Visitors give up before your page finishes loading, and the ones who stay have a worse experience, which shows up in lower engagement and fewer conversions. Google also uses Core Web Vitals, its real-user measures of loading, responsiveness and stability, as part of how it evaluates page experience.
The challenge is that “make the site faster” is vague. Speed problems usually come from a few specific sources: a slow server, oversized images, render-blocking code, or too much JavaScript. Once you know which one is hurting you, the fixes are well understood.
This guide shows you how to measure page speed properly, then walks through 15 practical fixes grouped by area, a step-by-step plan for prioritising them, and the mistakes that waste time in 2026.
Key Takeaways
- Measure with field data (real users) first and use lab tools to diagnose causes.
- Target Google's Core Web Vitals thresholds: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1.
- Server response time, images and JavaScript cause the majority of speed problems.
- Never lazy-load the main hero image; prioritise it instead.
- Fix shared templates and site-wide scripts first for the biggest impact.
How to measure page speed
PageSpeed Insights (PSI) is the best starting point because it shows two kinds of data. Field data comes from the Chrome User Experience Report and reflects real visitors over the previous 28 days. Lab data comes from Lighthouse, which simulates one page load on a fixed device and network. Field data tells you whether users have a problem; lab data helps explain why.
| Metric | What it tells you | Good target |
|---|---|---|
| Time to First Byte (TTFB) | How quickly the server starts responding | 0.8 s or less (rough guide) |
| Largest Contentful Paint (LCP) | When the main content appears | 2.5 s or less |
| Interaction to Next Paint (INP) | How quickly the page responds to input | 200 ms or less |
| Cumulative Layout Shift (CLS) | How much the layout jumps | 0.1 or less |
“As a rough guide, most sites should strive to have a TTFB of 0.8 seconds or less.”
— web.dev, Time to First Byte (TTFB)
For a site-wide view, use the Core Web Vitals report in Google Search Console, which groups similar URLs together. Read Core Web Vitals explained for a deeper look at each metric.
Which fixes help which metric?
| Area | Fixes (numbers below) | Main metric improved | Effort |
|---|---|---|---|
| Server and delivery | 1–4 | TTFB, LCP | Medium |
| Images and media | 5–9 | LCP, CLS | Low to medium |
| CSS and JavaScript | 10–13 | LCP, INP | Medium to high |
| Fonts and caching | 14–15 | LCP, CLS, repeat visits | Low |
15 practical fixes to improve page speed
1. Upgrade hosting and reduce server response time
Time to First Byte (TTFB) is the foundation for every other metric. Slow databases, overloaded shared hosting and uncached page generation all add delay before the browser receives anything.
2. Use page caching
Serve pre-built HTML instead of generating every page on each request. Most CMSs have caching plugins or server-level caching options.
3. Use a content delivery network (CDN)
A CDN stores copies of your files on servers around the world, cutting the distance data has to travel.
4. Minimise redirects
Every redirect adds a round trip. Link directly to final URLs and avoid chains; see our guide to 301 vs 302 redirects.
5. Compress and resize images
Serve images at the size they are displayed, not the size they were uploaded. Our image SEO guide covers compression in detail.
6. Use modern image formats
WebP and AVIF typically produce smaller files than JPEG or PNG at similar quality. Use the <picture> element for fallbacks if needed.
7. Prioritise the LCP image
Make sure the hero image is in the initial HTML and add fetchpriority="high". web.dev advises using high priority on only one or two images.
8. Lazy-load offscreen images only
Add loading="lazy" to images below the fold, but never to images likely to be visible on first load, especially the LCP image.
9. Set width and height on images and embeds
Explicit dimensions let the browser reserve space, preventing layout shifts and improving CLS.
10. Eliminate render-blocking CSS
Inline small amounts of critical CSS, defer the rest, and remove unused styles from bloated themes.
11. Defer or async non-critical JavaScript
Synchronous scripts in the <head> block rendering. Use defer for most scripts.
12. Audit third-party scripts
Chat widgets, heatmaps, social embeds and ad tags all compete for the main thread. Remove what you do not use and load the rest after interaction where possible.
13. Break up long JavaScript tasks
Long tasks block responsiveness and hurt INP. Split heavy work into smaller chunks and yield to the main thread.
14. Optimise web fonts
Limit font families and weights, self-host where possible, use font-display: swap and preload the main font file.
15. Enable compression and efficient caching
Serve text resources with Brotli or gzip compression and set long cache lifetimes for static assets with versioned filenames.
A step-by-step plan to speed up your site
- Benchmark. Record field data for your key templates (homepage, category, product or service, blog post) in PSI and Search Console.
- Find the bottleneck. For each failing template, identify the LCP element and its slowest sub-part, plus any long tasks and layout shifts.
- Pick quick wins. Image compression, correct lazy-loading, dimensions and caching often take hours, not weeks.
- Tackle structural issues. Hosting, theme bloat and third-party scripts need more planning and often a developer.
- Test before deploying. Compare lab results on a staging site, and check nothing breaks visually or functionally.
- Validate in the field. Watch field data over the next 28 days and use “Validate fix” in Search Console.
Common mistakes
- Chasing a perfect Lighthouse score. Real-user field data is what matters.
- Lazy-loading everything. Lazy-loading the hero image delays LCP.
- Stacking optimisation plugins. Multiple caching or minification plugins can conflict and break pages.
- Testing only on desktop and fast Wi-Fi. Most visitors browse on mobile networks; see our guide to mobile SEO.
- Forgetting third parties. Marketing tags added over the years often cost more than your own code.
- Treating speed as a one-off project. Every new plugin or campaign script can undo your gains.
Page speed, SEO and conversions
Speed is part of a bigger picture. It sits alongside crawlability, indexing and mobile experience in our technical SEO guide, and it directly supports conversion rate optimization: a faster checkout or contact form simply has less friction. If you are running paid campaigns, faster landing pages also improve the experience for every click you pay for. When you next run an SEO audit, include a performance review of your key templates.
Related Guides
- XML Sitemaps: How to Create and Submit One
- 301 vs 302 Redirects: Which One Should You Use?
- 404 Errors: How to Find and Fix Broken Pages
Frequently Asked Questions
What is a good page load time?
Rather than one load time, Google's Core Web Vitals give clear targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, for at least 75% of visits.
Does page speed affect SEO?
Yes, as part of page experience. Google recommends achieving good Core Web Vitals, but speed is one signal among many. Its bigger effect is often on bounce rate and conversions.
Why is my PageSpeed Insights score different every time?
The lab test simulates a single load, and results vary with server response, network conditions and third-party scripts. Field data from real users over 28 days is more stable and more meaningful.
Will a CDN make my site faster?
Usually, yes. A CDN serves static files, and often cached HTML, from servers closer to your visitors, which reduces latency and Time to First Byte, especially for international audiences.
Which fix should I do first?
Start with whatever is slowing your Largest Contentful Paint on your most important templates, typically oversized hero images, slow server response or render-blocking resources.
Conclusion
Improving page speed is about removing specific bottlenecks: a slow server, heavy images, render-blocking code and too much JavaScript. Measure with field data, fix the templates that matter most, and keep monitoring. If you would rather hand it to specialists, our page speed optimization service and conversion optimization team can make your site faster and more profitable. Get a free quote today.
