Does page speed affect rankings?

Confirmed Based on 35,176 data points

What the Data Shows

Pages loading under 1 second get the most impressions. The spread is ~63% — fast pages clearly attract more search visibility.

Bottom line: Sub-1s load time is a clear impressions advantage.

How to Read This Chart

The x-axis shows load time buckets from fastest to slowest. Each bar shows relative impressions for pages in that bucket. Look for the tallest bar under 1 second and the steady drop as load time increases. The full spread between buckets is about 63%.

Background

Many SEOs treat speed as a UX task, not a ranking task. That thinking leaves easy impressions on the table. We bucketed 35K+ unique pages by load time and compared relative impressions. Pages loading under 1 second got the most impressions, with a ~63% spread between speed buckets.

What to Do Next

  1. 1

    Pull top 50 landing pages and map their speed bucket high

    Split by <1s, 1–2s, 2–3s, and 3s+ to see where impressions are trapped.

  2. 2

    Find the biggest byte sources on one slow template high

    Use DevTools Coverage and Network to list top JS and image payloads.

  3. 3

    Cut one third-party script from key templates medium

    Remove or delay the worst offender and re-check field metrics after rollout.

  4. 4

    Set performance budgets in CI for LCP and JS weight low

    Fail builds when templates exceed agreed limits.

Best Practices

  1. 1

    Hit LCP under 2.5s

    LCP tracks when the main content becomes useful. Miss it and you lose visibility on competitive queries.

  2. 2

    Keep TTFB under 800ms

    Slow servers delay every render step and every bot fetch. High TTFB can cap crawl and slow re-ranking after updates.

  3. 3

    Ship under 150KB of JS on key templates

    Heavy JS delays interactivity and can block rendering. Too much JS also raises CPU time on mobile devices.

  4. 4

    Compress images and serve next-gen formats

    Images are often the biggest bytes on the page. Uncompressed images push pages out of the fast bucket.

Common Mistakes to Avoid

  • Testing only on desktop

    Desktop hides mobile CPU and network delays, so you miss the real bottleneck.

  • Optimizing lab scores while field stays slow

    Lighthouse wins do not guarantee better real-user speed or more impressions.

  • Fixing one page instead of the template

    Single-page tweaks do not move the site-wide distribution that search sees.

What Works

  • + More impressions from better eligibility on fast SERP features and mobile-heavy queries.
  • + Higher crawl efficiency when bot fetches complete faster and timeouts drop.
  • + Faster re-ranking after updates because pages render and get processed sooner.

What Doesn’t

  • - Chasing perfect Lighthouse scores can waste time with no field speed change.
  • - Extra tags, A/B tools, and chat widgets often wipe out speed gains.
  • - Over-compressing images can hurt quality and conversions without real speed wins.

Expert Tip

Speed gains that move rankings usually come from removing work, not tuning settings. Strip third-party scripts first, then reduce JS execution on the main thread. Many sites improve load time but leave render-blocking JS, so the page still feels slow and stays in a worse bucket.

Frequently Asked Questions

Does page speed affect Google rankings?
Yes. Faster pages in our dataset earned more impressions, and the gap was large.
What load time should I aim for to compete?
Aim for under 1 second on key entry pages. Also keep Core Web Vitals in the good range.
Is page speed only a tie-breaker?
Not in this data. The impression spread across speed buckets is too wide to treat as minor.
Can I rank with a slow site if content is great?
Sometimes, but you will fight a headwind. Speed can limit impressions even when relevance is strong.
Will adding a CDN automatically fix rankings?
Not by itself. If JS, images, and server work are still heavy, the page can stay slow.
Share: Post Share
Methodology

All data comes from real websites tracked by SEOJuice. We use the latest snapshot per page so each page counts once, regardless of site size. We filter for pages with at least 10 Google Search Console impressions and valid ranking positions (1-100).

Data is refreshed weekly. Correlation does not imply causation — these insights show associations, not guaranteed outcomes.

Want to check these metrics for your site?

SEOJuice tracks all these metrics automatically and helps you improve them.

Try SEOJuice Free