PageSpeed Tips Guide — Boost Your Score Above 90

Updated 2025 · Prioritized by impact · Starting with images (the biggest win)

What Is Google PageSpeed Insights and Why Does Your Score Matter?

Google PageSpeed Insights (PSI) analyzes your pages and assigns a score from 0–100 based on performance metrics. Google uses these same metrics — especially Core Web Vitals — as ranking signals. A slow page is a penalized page.

Score Ranges

┌─────────────────────────────────────────────────────────────┐
│               PageSpeed Insights Score Ranges                │
├──────────────────┬──────────────────────┬───────────────────┤
│    Poor ❌        │  Needs Improvement ⚠️│    Good ✅         │
│     0 – 49       │       50 – 89        │    90 – 100        │
│                  │                      │                    │
│  ████████████░   │  ██████████████████░ │  ██████████████████│
│  Ranking penalty │  Work required       │  Your target       │
│  on mobile       │                      │  (especially mobile│
└──────────────────┴──────────────────────┴───────────────────┘

Always test mobile first. Google uses mobile-first indexing — your mobile PageSpeed score is what matters most for rankings. Mobile scores are typically 20–30 points lower than desktop. Start your optimization there.

How PageSpeed Connects to SEO

Poor PageSpeed score
        │
        ▼
Poor Core Web Vitals (LCP, CLS, INP)
        │
        ▼
Negative Google ranking signals
        │
        ▼
Lower position in search results
        │
        ▼
Less organic traffic and conversions

The virtuous cycle runs in reverse: better images → better PSI score → better Core Web Vitals → higher rankings.

All Tips Ranked by Impact

Tier 1 — Highest Impact 🔥

#	Tip	Expected Score Improvement
1	Convert images to WebP	+15–25 points
2	Preload your LCP image	+10–20 points (LCP)
3	Set width & height on all images	Eliminates CLS entirely
4	Lazy load below-fold images	+5–15 points

Tier 2 — Medium Impact ⚡

#	Tip	Expected Score Improvement
5	Serve images via CDN	+5–10 points
6	Use responsive images (srcset)	+3–8 points
7	Defer non-critical JavaScript	+5–15 points (TBT)
8	Load fonts with `font-display: swap`	+2–5 points

Detailed Breakdown of Each Tip

Tip 1 — Convert Images to WebP ⚡ Highest Impact

The single biggest PageSpeed win available on most sites. WebP is 25–35% smaller than JPG at the same quality. Use our free converter — instant, no file uploads. Read the complete WebP guide for full implementation details.

Tip 2 — Preload Your LCP Image ⚡ Highest Impact

Add this line to your <head> to tell the browser to load your hero image immediately:

<link rel="preload" as="image" href="hero.webp">

This single change typically reduces LCP by 0.5–1.5 seconds — often the largest single improvement you can make.

Tip 3 — Add `width` & `height` to Images ⚡ High Impact (CLS)

Without explicit dimensions, the browser can’t reserve space for an image before it loads. Content jumps when the image appears, causing CLS:

<!-- ❌ Bad — causes CLS -->
<img src="photo.webp" alt="Product">

<!-- ✅ Good — prevents CLS -->
<img src="photo.webp" alt="Product" width="800" height="600">

Tip 4 — Lazy Load Below-Fold Images ⚡ High Impact

<!-- Only for images below the visible viewport -->
<img src="content.webp" loading="lazy" alt="...">

Critical warning: Never add loading="lazy" to your hero/LCP image — this will significantly hurt your LCP score and is one of the most common PageSpeed mistakes made.

Tip 5 — Use a CDN for Images ● Medium Impact

Serve images from a CDN (Cloudflare, Bunny.net, CloudFront) to reduce latency. Users receive images from a server geographically close to them. Cloudflare’s free plan handles most sites.

Tip 6 — Serve Responsive Images (srcset) ● Medium Impact

A 1600px image served to a 375px mobile screen wastes 4× the bandwidth:

<img
  srcset="image-400.webp 400w, image-800.webp 800w, image-1600.webp 1600w"
  sizes="(max-width: 600px) 400px, (max-width: 1200px) 800px, 1600px"
  src="image-800.webp"
  alt="..."
>

Read our image formats guide for more on responsive delivery.

Tip 7 — Defer Non-Critical JavaScript ● Medium Impact

<!-- Defer non-critical scripts -->
<script src="analytics.js" defer></script>
<script src="widget.js" async></script>

Render-blocking JavaScript delays LCP and increases Total Blocking Time (TBT) — both heavily penalized by PSI.

Tip 8 — Load Fonts with `display=swap` ● Medium Impact

@font-face{ 
  font-family: 'MyFont';
  src: url('font.woff2') format('woff2');
  font-display: swap; /* Prevents invisible text during font load */
 }

Also add preconnect for external font CDNs in your <head>:

<link rel="preconnect" href="https://fonts.googleapis.com" crossorigin>

The Image Audit — Fixing the 3 Most Common PSI Warnings

┌────────────────────────────────────────────────────────────────────┐
│     Lighthouse / PSI Image Warnings and How to Fix Them            │
├────────────────────────────────────────────────────────────────────┤
│                                                                    │
│  ⚠️  "Serve images in next-gen formats"                            │
│      Fix: Convert all images to WebP                               │
│      Tool: MixsMix free converter or follow the WebP guide         │
│                                                                    │
│  ⚠️  "Efficiently encode images"                                   │
│      Fix: Compress to 75–85% quality                               │
│      Guide: See compression guide for per-type settings            │
│                                                                    │
│  ⚠️  "Properly size images"                                        │
│      Fix: Serve at display dimensions + use srcset                 │
│      Guide: Batch resize with the batch convert guide              │
│                                                                    │
└────────────────────────────────────────────────────────────────────┘

How to Read and Act on Your PageSpeed Report

Step 1 — Run the test.
Go to pagespeed.web.dev, enter your URL, and test both mobile and desktop separately.

Step 2 — Check the Opportunities section.
These are the fixes with the highest estimated time savings. Always address these first — they have the most direct impact on your score.

Step 3 — Check Diagnostics.
Best-practice violations without a direct time saving estimate, but they still matter for user experience and rankings.

Step 4 — Focus on mobile.
Google’s ranking algorithm uses your mobile score. A desktop score of 95 means nothing if your mobile score is 42.

Step 5 — Retest after changes.
PSI lab scores can vary between runs. Test 3 times and take the average. Use WebPageTest for more controlled lab data.

PageSpeed Optimization Roadmap

Phase 1 — Week 1: Images (biggest wins)
  ├── Convert all images to WebP
  ├── Compress to 75–85% quality
  └── Add width/height to all img tags

Phase 2 — Week 2: Loading Strategy
  ├── Add preload for LCP image
  ├── Add lazy loading for below-fold images
  └── Implement srcset for responsive images

Phase 3 — Week 3: Infrastructure
  ├── Set up CDN (Cloudflare free tier)
  ├── Defer non-critical JavaScript
  └── Add font-display: swap for web fonts

Phase 4 — Ongoing: Measure & Iterate
  ├── Run PSI before/after each change
  ├── Monitor Core Web Vitals in Search Console
  └── Track real-user data from CrUX

Expected Score Improvements by Steps Applied

Steps Applied	Expected Score Improvement
WebP conversion only	+10–20 points
WebP + LCP preload	+20–30 points
Tips 1–4 complete	+25–40 points
All 8 tips applied	+30–50 points

The first four tips alone typically add 15–30 points to your mobile score. That’s often the difference between red and green.

Frequently Asked Questions

What is a good PageSpeed Insights score?
A score of 90–100 is considered “Good” by Google. 50–89 is “Needs Improvement”. Below 50 is “Poor”. Aim for 90+ on mobile — that’s Google’s primary benchmark since mobile-first indexing became the default.

Does PageSpeed Insights score affect SEO rankings?
Yes, indirectly. Google uses Core Web Vitals (LCP, CLS, INP) as ranking signals — these are the same metrics PSI measures. A poor PSI score means poor Core Web Vitals, which negatively affects your search rankings.

Why does my PageSpeed score vary between tests?
PSI lab scores can vary due to network conditions, server response time variability, and Chrome’s rendering behavior. For consistent results, run 3–5 tests and average the scores. The “Field Data” section (real user data from CrUX) is more reliable but takes weeks to update after changes.

What is the fastest way to improve my PageSpeed score?
The fastest wins, in order: (1) Convert all images to WebP and compress to 80–85% quality. (2) Preload your LCP image with rel="preload". (3) Add loading="lazy" to below-fold images. (4) Add width and height to all images to eliminate CLS. These four steps alone typically add 15–30 points to your mobile score.

Authoritative External Resources

Related Guides

Last updated: May 2025 · MixsMix — Free Image Converter