What is Page Speed?
Page speed is how quickly the content on a web page loads for a user. It's measured by multiple metrics — Time to First Byte (TTFB), First Contentful Paint (FCP), and the Core Web Vitals (LCP, INP, CLS). Google has used page speed as a ranking signal since 2010 and formalised it with the 2021 Page Experience update. Beyond rankings, faster pages directly improve conversion rates and reduce bounce rates.
- PageSpeed Insights (free, from Google) gives you a score and specific fix recommendations — start there.
- The biggest page speed wins are almost always image optimisation: compress, resize, and use modern formats (WebP/AVIF).
- Third-party scripts (analytics, chat widgets, ad scripts) are often the hidden cause of slow page loads.
- Server response time (Time to First Byte) is the foundation — no front-end optimisation compensates for a slow server.
- Next.js handles many page speed best practices automatically: code splitting, lazy loading, and image optimisation via next/image.
What Affects Page Speed
Images: unoptimised images are the most common cause of slow pages. Large, uncompressed images can add several seconds to load time. Fix: compress images, use next/image or similar for automatic resizing and lazy loading, and serve modern formats.
JavaScript: excessive JS bundle size delays page interactivity. Fix: code-split, lazy-load non-critical scripts, and audit third-party scripts.
Server response time: if the server takes more than 200ms to respond, everything else is delayed. Fix: upgrade hosting, use a CDN, implement server-side caching.
Render-blocking resources: CSS and JS that blocks the browser from rendering content. Fix: defer non-critical JS, inline critical CSS.
Page Speed Tools
PageSpeed Insights (pagespeed.web.dev): Google's free tool combining Lighthouse (lab data) and Core Web Vitals field data. Start here — it gives page-level fix recommendations.
Google Search Console → Core Web Vitals: shows field data across your entire site, grouped by good/needs improvement/poor URLs.
WebPageTest.org: detailed waterfall analysis showing exactly which resources are slowing your page. Useful for diagnosing specific bottlenecks.
For Next.js sites: the built-in next/image component, automatic code splitting, and Edge Runtime all contribute to strong page speed scores by default.
Most guides are already outdated.
One email a week. The search stuff that actually matters — what shifted, what died, and what to do about it.
Subscribe free →Google officially announces page speed as a ranking factor for desktop searches, the first time load performance directly influenced rankings.
Google extends page speed as a ranking signal to mobile searches, reflecting the shift to mobile-first indexing.
Google introduces LCP, FID (later replaced by INP), and CLS as standardised, user-centric metrics for measuring real-world page experience.
Core Web Vitals become official ranking signals via the Page Experience update, formalising the link between user experience metrics and search rankings.
Interaction to Next Paint (INP) replaces First Input Delay (FID) as a Core Web Vital, providing a more comprehensive measure of page interactivity.
Run your URL through pagespeed.web.dev. Review both the Lighthouse lab score and the Core Web Vitals field data. Note which metrics are marked Poor or Needs Improvement — these are your priorities.
Use the Opportunities and Diagnostics sections in PageSpeed Insights to find the highest-impact issues. If you need a deeper waterfall view, load the URL in WebPageTest.org to see exactly which resources are causing delays.
Images are the most common culprit. Compress files, convert to WebP or AVIF, add explicit width and height attributes to prevent layout shift, and enable lazy loading for below-the-fold images.
Use Chrome DevTools Coverage tab to find unused JS. Remove or defer third-party scripts that are not business-critical. If using a framework, enable code splitting so only required code loads per page.
After deploying fixes, allow 28 days for Google Search Console Core Web Vitals field data to refresh. Lab scores improve immediately; real-user data reflects the actual experience across all visitors and devices.
How does your site score on SEO?
Paste your URL. Get a score and a fix list across all three disciplines. No form, no email.
Run Free Audit →Frequently Asked Questions
Yes, but it's a lightweight signal. Google confirmed page speed as a ranking factor in 2010 (desktop) and 2018 (mobile). The Page Experience update in 2021 formalised Core Web Vitals as ranking signals. In practice, page speed is more of a floor — failing it doesn't cause a ranking collapse, but it can be the tiebreaker between two otherwise equal pages.
Lighthouse runs in a controlled lab environment. Real-world performance depends on user device, network speed, browser, and third-party scripts. A perfect Lighthouse score means the page is technically optimised — but field data (from real Chrome users via CrUX) is what Google actually uses for ranking. Check Core Web Vitals in Search Console for real-world data.
- 1.Google PageSpeed Insights
- 2.Google — Page Experience documentation
- 3.web.dev — Web Vitals
Read next
Technical SEO
Technical SEO is the practice of optimising the infrastructure of your website so search engines can efficient…
Core Web Vitals
Core Web Vitals are a set of three Google-defined metrics that measure real-world user experience on a webpage…
Crawl Budget
Crawl budget is the number of pages Googlebot will crawl on your website within a given timeframe. It's determ…
Mobile-First Indexing
Mobile-first indexing means Google primarily uses the mobile version of a website's content to index and rank…