What Is Page Speed?
Page speed refers to how quickly a web page loads its content and becomes interactive for the user. It encompasses everything from the initial server response to the final paint of all visible elements. Page speed is measured through several metrics that capture different aspects of the loading experience.
It is important to distinguish between page speed and site speed. Page speed refers to how fast an individual page loads, while site speed is the average performance across all pages on your website. Both matter, but individual page performance varies significantly based on content, images, scripts, and server configuration.
Why Page Speed Matters for SEO
Google has used page speed as a ranking factor since 2010 for desktop and since 2018 for mobile (the "Speed Update"). In 2021, Google introduced Core Web Vitals as a more specific set of speed-related ranking signals. The impact of page speed on SEO works through several channels:
Direct ranking signal
Google's algorithms factor page speed into ranking decisions. While content relevance and backlinks carry more weight, page speed acts as a tiebreaker between pages of similar quality. For competitive queries where dozens of pages have good content, speed can determine who ranks on page one versus page two.
User experience and engagement
Slow pages cause users to bounce. Research from Google shows that as page load time increases from 1 second to 3 seconds, the probability of bounce increases by 32%. From 1 to 5 seconds, bounce probability increases by 90%. High bounce rates and low engagement signal to Google that users are not satisfied with the result.
Crawl efficiency
Faster pages allow Google to crawl more of your site within its allocated crawl budget. If your pages are slow, Googlebot spends more time per page and may not reach all your content before moving on.
Mobile-first indexing
Since Google uses mobile-first indexing, your mobile page speed is what matters most. Mobile users are often on slower connections, making speed optimisation even more critical.
Key Page Speed Metrics
| Metric | What It Measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | Time until the largest visible element loads | < 2.5s | > 4.0s |
| FCP (First Contentful Paint) | Time until the first text/image appears | < 1.8s | > 3.0s |
| CLS (Cumulative Layout Shift) | How much the page layout shifts during loading | < 0.1 | > 0.25 |
| INP (Interaction to Next Paint) | Responsiveness to user interactions | < 200ms | > 500ms |
| TBT (Total Blocking Time) | Time the main thread is blocked by scripts | < 200ms | > 600ms |
| Speed Index | How quickly visible content is progressively loaded | < 3.4s | > 5.8s |
| TTFB (Time to First Byte) | Time until the server sends the first byte of data | < 200ms | > 600ms |
How to Test Page Speed
There are several ways to test your page speed:
- RankNibbler — run an SEO audit and check the Performance tab. It uses Google's PageSpeed Insights API to test your page and return scores, Core Web Vitals, and specific recommendations.
- Google PageSpeed Insights — Google's own tool at pagespeed.web.dev. Provides both lab data (simulated) and field data (real users).
- Chrome DevTools — the Lighthouse tab in Chrome's developer tools runs a full performance audit locally.
- Google Search Console — the Core Web Vitals report shows real-world performance data from Chrome users visiting your site.
What Slows Down a Page
The most common causes of slow pages:
- Uncompressed images — often the single biggest factor. Use WebP format, compress before uploading, and add lazy loading. See our image optimisation guide.
- Too many external scripts — each JavaScript file requires a network request. Check your CSS/JS file count and ensure scripts use async or defer.
- Render-blocking CSS — CSS in the head blocks the page from rendering until it downloads. Inline critical CSS and defer the rest.
- Slow server response — cheap shared hosting, no caching, or a server far from your users. Use a CDN and enable server-side caching.
- Too many HTTP requests — every resource (image, script, stylesheet, font) requires a separate request. Combine files and reduce the total.
- No browser caching — without cache headers, returning visitors re-download everything.
- Unminified code — HTML, CSS, and JavaScript with unnecessary whitespace and comments.
- Web fonts — custom fonts add extra downloads. Use font-display: swap and preload critical fonts.
How to Improve Page Speed
For a detailed guide with specific techniques, see our page load time reduction guide. The quick wins that make the biggest difference:
- Compress and resize images (biggest impact for most sites)
- Add
loading="lazy"to below-fold images - Add
asyncordeferto all non-critical scripts - Enable GZIP or Brotli compression on your server
- Use a CDN (Cloudflare is free)
- Set browser cache headers on static resources
Last updated: March 2026