What Is Page Speed?
Page speed is how quickly a page loads and becomes usable. What affects it, how to fix it, and a real example.
Page speed is how quickly a webpage’s content loads and becomes usable for a visitor. It’s influenced by server response time, file sizes, and how efficiently a page is coded, and it feeds directly into the Core Web Vitals metrics Google uses for ranking.
Why page speed matters
Slow page speed increases the chance a visitor abandons the page before it even finishes loading, directly hurting conversions and engagement, a cost that shows up in your business metrics well before it shows up in any ranking report. It also feeds into Core Web Vitals metrics like LCP, making it relevant to rankings as well as raw user experience. The two effects compound: a slow page loses both the visitors who bounce before it loads and the ranking position that would have brought more visitors in the first place.
What affects page speed
- Server response time. How quickly the hosting infrastructure responds to the initial request, before any content even starts downloading.
- Image and media file sizes. Large, uncompressed images are consistently one of the biggest contributors to slow-loading pages.
- Render-blocking CSS and JavaScript. Resources the browser must process before displaying any visible content.
- Number of third-party scripts. Ad networks, analytics, chat widgets, and embeds each add their own loading overhead outside your direct control.
- Caching and CDN usage. Whether repeat visitors and geographically distant users get served efficiently or re-fetch everything from scratch.
How to improve page speed
- Compress and serve images in next-gen formats like WebP or AVIF, one of the highest-impact, lowest-effort fixes available.
- Use a CDN to serve content from locations closer to your visitors, reducing latency.
- Minimize and defer non-critical JavaScript and CSS.
- Enable browser caching so repeat visitors don’t re-download unchanged assets.
- Audit and reduce third-party scripts, each one you remove is guaranteed overhead eliminated.
Page speed vs. Core Web Vitals
| Term | What it refers to |
|---|---|
| Page speed | General, broad concept of how fast a page loads and becomes usable |
| Core Web Vitals | Specific, standardized metrics (LCP, INP, CLS) Google uses to measure aspects of speed and experience |
Real example
For example, a product page loaded with uncompressed, full-resolution images might take 6 seconds to load on mobile, while the same page with compressed images and lazy loading could load in under 2 seconds, a change that directly affects both bounce rate and the page’s LCP score.
Page speed and AI search
Page speed doesn’t directly influence AI Overview citation eligibility, which depends on content relevance, but a slow-loading destination undermines the value of any citation, a visitor who clicks through from an AI-generated answer and waits several seconds for content to appear is more likely to abandon before ever engaging with the content that earned the citation in the first place.
FAQ
What’s a good page speed target?
Rather than a single generic number, aim to pass Core Web Vitals thresholds specifically, LCP under 2.5 seconds, since these are the standardized, measured targets Google actually evaluates.
Do images really matter that much for page speed?
Yes, they’re consistently one of the largest contributors to page weight and slow load times on most sites, compressing and properly sizing images is often the single highest-impact fix available.
How do I test my page speed?
Google PageSpeed Insights and Search Console’s Core Web Vitals report both provide direct measurement, combining lab data with real user field data for a complete picture.
Can hosting alone fix a slow site?
Better hosting helps server response time specifically, but it won’t fix front-end issues like unoptimized images or excessive JavaScript, a genuinely fast site usually needs improvements on both the server and front-end side.
Related terms
Every second your page takes to load is a visitor deciding whether to wait or leave. Compress the images first, it’s the cheapest, fastest win available.