# Page speed

Category: [Performance & Core Web Vitals](https://seo-geo-glossary.com/en/glossary/category/performance-core-web-vitals/) › [Basics & measurement](https://seo-geo-glossary.com/en/glossary/category/performance-core-web-vitals/basics-measurement/) · Also known as: site speed, page load time, PageSpeed

**Page speed** is how quickly a web page loads, becomes visible, and responds to user input. In SEO the term often also refers to Google's free testing tool PageSpeed Insights, which measures a URL and suggests improvements. Site speed is the same idea applied to a whole website.

## How is page speed measured?

No single number captures "load time." Google measures speed with several metrics. The three Core Web Vitals are Largest Contentful Paint (LCP, when the largest visible element has loaded), Interaction to Next Paint (INP, how quickly the page responds to input), and Cumulative Layout Shift (CLS, how much content moves while loading). Supporting metrics include First Contentful Paint and Time to First Byte.

PageSpeed Insights reports two kinds of data:

- **Field data** comes from the Chrome User Experience Report (CrUX). It shows how fast the page was for real Chrome users over the previous 28 days.
- **Lab data** comes from a simulated page load with Lighthouse on a defined device and network. From it, Lighthouse calculates a performance score from 0 to 100.

The two can differ a lot. Field data reflects real devices and connections. Lab data is reproducible and useful for tracing a specific problem.

## Does page speed affect rankings?

Google states that Core Web Vitals are used by its ranking systems. According to Google there is no single page experience signal, and relevance comes first. Google Search shows the most relevant content even if its page experience is below average. Where many pages are similarly helpful, good page experience can make a difference.

## Example

Google rates each metric at the 75th percentile of page loads:

| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP | up to 2.5 s | up to 4.0 s | over 4.0 s |
| INP | up to 200 ms | up to 500 ms | over 500 ms |
| CLS | up to 0.1 | up to 0.25 | over 0.25 |

A product page with a field LCP of 3.1 seconds at the 75th percentile needs improvement, even if Lighthouse gives it a lab score of 92.

## Common mistakes

- **Optimizing only for the Lighthouse score.** The score comes from lab data. Google notes that lab data may not capture real-world bottlenecks. Field data shows what real users experience.
- **Equating good scores with top rankings.** Google says good results in Search Console's Core Web Vitals report or in third-party tools don't guarantee top rankings. Relevance comes first.
- **Improving a single metric.** Google advises site owners not to focus on only one or two aspects of page experience.
- **Testing only on desktop.** PageSpeed Insights tests mobile and desktop separately, on mobile with a mid-tier phone on a mobile network. The results can differ a lot.

## FAQ

**What is a good PageSpeed score?**
In Lighthouse, 90 or higher is good (green), 50 to 89 needs improvement (orange), and below 50 is poor (red). The score is based on lab data.

**Why does PageSpeed Insights show no field data for my page?**
CrUX only includes pages and origins with enough traffic from Chrome users. Without it, PageSpeed Insights shows lab data only.

**Is there a free page speed test?**
Yes. PageSpeed Insights at pagespeed.web.dev is free, and Lighthouse is built into Chrome DevTools.

## At a glance

- **Type:** umbrella term for load time metrics
- **Values:** Core Web Vitals LCP, INP, CLS (75th percentile)
- **Data sources:** field data (CrUX, 28 days) and lab data (Lighthouse)
- **Affects:** user experience; ranking via Core Web Vitals
- **Docs:** [About PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about)

Last checked: October 8, 2026

## Thresholds

- **LCP** (Largest Contentful Paint): good ≤ 2.5 s, needs improvement ≤ 4 s, poor > 4 s ([Source](https://web.dev/articles/lcp))
- **INP** (Interaction to Next Paint): good ≤ 200 ms, needs improvement ≤ 500 ms, poor > 500 ms ([Source](https://web.dev/articles/inp))
- **CLS** (Cumulative Layout Shift): good ≤ 0.1, needs improvement ≤ 0.25, poor > 0.25 ([Source](https://web.dev/articles/cls))

Assessed at the 75th percentile of page loads, mobile and desktop separately.

## Related terms

- [Core Web Vitals](https://seo-geo-glossary.com/en/glossary/core-web-vitals/index.md)
- [Largest Contentful Paint (LCP)](https://seo-geo-glossary.com/en/glossary/largest-contentful-paint/index.md)
- [Interaction to Next Paint (INP)](https://seo-geo-glossary.com/en/glossary/interaction-to-next-paint/index.md)
- [Cumulative Layout Shift (CLS)](https://seo-geo-glossary.com/en/glossary/cumulative-layout-shift/index.md)
- [PageSpeed Insights](https://seo-geo-glossary.com/en/glossary/pagespeed-insights/index.md)
- [Lighthouse](https://seo-geo-glossary.com/en/glossary/lighthouse/index.md)
- [Chrome UX Report (CrUX)](https://seo-geo-glossary.com/en/glossary/chrome-ux-report/index.md)
- [Speed Index](https://seo-geo-glossary.com/en/glossary/speed-index/index.md)
- [Page experience](https://seo-geo-glossary.com/en/glossary/page-experience/index.md)

## More on the searchVIU blog

- [Case study: 28% page speed improvement with Cloudflare HTML caching](https://www.searchviu.com/en/html-caching-cloudflare-ecommerce/)

## Sources

- [About PageSpeed Insights – Google for Developers (last updated 2024-10-21)](https://developers.google.com/speed/docs/insights/v5/about)
- [Understanding page experience in Google Search results – Google Search Central (last updated 2026-09-22)](https://developers.google.com/search/docs/appearance/page-experience)
- [Web Vitals – web.dev](https://web.dev/articles/vitals)
- [Is PageSpeed Insights reliable? – DebugBear (secondary source)](https://www.debugbear.com/blog/is-pagespeed-insights-reliable)

---

Last updated: October 8, 2026
URL: https://seo-geo-glossary.com/en/glossary/page-speed/