Page speed

Page speed is how quickly a web page loads and becomes usable for visitors. Google measures the user-facing side through Core Web Vitals; faster pages tend to rank a little better and keep more visitors.

Page speed is a broad term. It can mean how fast the server responds, how quickly something appears on screen, when the main content is visible or when the page reacts to input. Because one number cannot capture all of that, it is more useful to look at several metrics:

  • Time to First Byte (TTFB): how long the server takes to start sending the page.
  • First Contentful Paint (FCP): when the first text or image appears.
  • Largest Contentful Paint (LCP): when the main content is visible.
  • Interaction to Next Paint (INP): how quickly the page responds to clicks and taps.
  • Cumulative Layout Shift (CLS): whether the layout stays stable while loading.

LCP, INP and CLS together form Google's Core Web Vitals, which are what Google uses for page experience.

Speed and SEO. Google has used speed as a ranking signal for desktop since 2010 and for mobile since 2018, and today it does so through Core Web Vitals. The effect is real but modest: relevance and quality come first. Speed matters more for business results. Slow pages lose visitors before they have seen anything, especially on mobile connections, and that costs leads and sales regardless of rankings.

Speed and crawling. A fast server also helps Google crawl more. On large sites, slow response times reduce the number of pages Googlebot fetches, which delays indexing of new content.

Tools:

  • PageSpeed Insights combines real-user field data from the Chrome User Experience Report with a Lighthouse lab test.
  • Lighthouse in Chrome DevTools runs a lab test with concrete suggestions.
  • The Core Web Vitals report in Google Search Console groups URLs by status.
  • The Performance panel in Chrome DevTools shows exactly what the browser is doing over time.

What usually makes the biggest difference:

  1. Good hosting, server-side caching and a CDN for faster TTFB.
  2. Compressed, correctly sized images in WebP or AVIF, with lazy loading below the fold only.
  3. Less JavaScript: remove unused plugins, delay non-essential scripts and audit third-party tags.
  4. Critical CSS inline and the rest loaded without blocking rendering.
  5. Efficient font loading with a limited number of font files.

Common mistakes. Treating the Lighthouse score as the goal is the classic one. That score is a lab simulation; a page can score 95 and still fail Core Web Vitals in the field, or score 60 and pass. Another mistake is optimising once and then letting new plugins, tracking pixels and widgets slowly pile up. Speed needs a budget and a regular check, just like content.

For publishers, speed also affects how attractive a site is for advertisers. A fast, stable article page keeps readers on the page longer, which is good for the publisher's own metrics and for every link placed in that content.

Questions about Page speed

Is page speed a Google ranking factor?

Yes, through Core Web Vitals and page experience, but it is a modest factor. Relevance and content quality weigh much more heavily.

What is a good PageSpeed Insights score?

Focus on the field data at the top of the report rather than the lab score. Passing Core Web Vitals with real users matters more than reaching 100 in Lighthouse.

What slows down a website most?

Usually heavy images, too much JavaScript from plugins and third-party tags, and a slow server. Fixing those three often solves most speed problems.

Related terms