PageSpeed Insights Says "Efficiently Encode Images" — What to Actually Do

You ran your page through PageSpeed Insights, and there it is under Opportunities: "Efficiently encode images — Potential savings of 1,240 KB." It's one of the most common audits on the entire web, and also one of the most misunderstood. Most people either ignore it or install a plugin and hope.

This guide explains exactly what triggers the warning, how to calculate what Google actually wants, and how to clear it permanently — including the three cases where the warning is safe to leave alone.

---

Table of Contents

1. What the Warning Actually Means
2. How Google Calculates the Savings Number
3. Related Audits You'll See Alongside It
4. How to Read the Report Correctly
5. The Fix, Step by Step
6. Choosing the Right Quality Setting
7. When You Can Safely Ignore the Warning
8. Verifying the Fix
9. Frequently Asked Questions

---

1. What the Warning Actually Means

"Efficiently encode images" fires when Lighthouse determines that one or more images on your page could be meaningfully smaller at the same visual quality, using the same format.

This is a compression audit, not a format audit and not a dimensions audit. Lighthouse is telling you: this JPEG is encoded at a higher quality level than it needs to be. It is not telling you to switch to WebP, and it is not telling you the image is too large in pixels — those are separate audits that people constantly confuse with this one.

The warning appears in the Opportunities section of the Performance report. Opportunities are lab-based estimates. They do not directly change your score; they suggest where your score is coming from. Your actual Performance score is driven by the metrics themselves — chiefly LCP.

---

2. How Google Calculates the Savings Number

Lighthouse's method is more mechanical than most people realize:

1. It takes each JPEG on the page.
2. It re-encodes that image internally at quality level 85.
3. It compares the re-encoded size to the size you're actually serving.
4. If the difference exceeds roughly 4 KB, the image is flagged.
5. All flagged savings are summed into the headline "Potential savings" figure.

Two consequences follow directly from this:

• The target is quality 85. If you export your JPEGs at 85 or below, this audit will not fire for those images. That's the whole rule.
• The audit is JPEG-centric in its estimate. PNGs and other formats are handled differently and are more often flagged by the next-gen formats audit instead.

---

3. Related Audits You'll See Alongside It

Half the confusion around this warning comes from people applying the fix for a different audit. Here's how the four image audits divide up.

If you fix all four, you fix essentially the entire image side of your performance profile. But apply them in the right order: resize first, then convert format, then compress. Doing it in the reverse order means you compress pixels you're about to throw away.

---

4. How to Read the Report Correctly

How to extract the actual fix list

1. Run the page through PageSpeed Insights and scroll to Opportunities.
2. Expand "Efficiently encode images." You'll get a table with three columns: URL, Resource Size, and Potential Savings.
3. Sort mentally by Potential Savings, not by resource size. A 900 KB image saving 40 KB matters less than a 300 KB image saving 250 KB.
4. Check the mobile tab separately from desktop. Mobile runs on a throttled simulated connection, so the same savings translate to a much bigger time cost.
5. Cross-reference with your LCP element. Under Diagnostics, find "Largest Contentful Paint element." If that image is in your savings list, it is your single highest-priority fix — it affects a Core Web Vital directly, not just a lab opportunity.
6. Copy the URLs into a list. These are the exact files you need to re-encode. You usually do not need to touch every image on the site.

---

5. The Fix, Step by Step

How to clear the audit

1. Download the flagged originals from your media library or asset folder — not from the live page, since a CDN may already have transformed them.
2. Resize them to their maximum displayed width first. If your content column is 800px wide, a 3000px source is wasted. Export at 2× the display width for retina (1600px) and no more.
3. Re-encode at quality 80–85. This is the single step that clears the audit. Compressing in the browser at CompressFile.pro does this without uploading files anywhere, which is faster than any server-side pipeline and keeps client assets private.
4. Convert format while you're there. Since you're re-encoding anyway, export WebP or AVIF as well — that clears the next-gen formats audit in the same pass.
5. Replace the files and purge your CDN cache. This step is skipped constantly; a stale CDN will keep serving the old bytes and you'll think the fix failed.
6. Add width and height attributes to the corresponding <img> tags if they're missing. Different audit, but you're already in the template.
7. Re-run PageSpeed Insights and confirm the audit has moved from Opportunities to Passed Audits.

For a site with hundreds of flagged images, work by template rather than by file: fix the hero image pattern, the product card pattern, and the article body pattern, and you'll typically clear 90% of the flagged volume.

---

6. Choosing the Right Quality Setting

Quality settings are not linear and are not comparable across formats. Here's what each range actually gets you on a photographic image.

The important insight: moving from quality 100 to quality 85 cuts file size by roughly two-thirds and is invisible to essentially every viewer. Moving from 85 to 70 saves another 10 percentage points and is sometimes visible. The first move is free; the second one has a cost.

Images with large areas of smooth gradient — skies, studio backdrops, soft shadows — degrade earlier than busy, detailed images. If you have a mixed library, test the gradients.

---

7. When You Can Safely Ignore the Warning

Not every flagged image needs action.

• The savings are trivial. A total potential saving under 50 KB on a page is noise. Spend the time on something else.
• The image is genuinely detail-critical. Product zoom images, jewellery close-ups, medical or scientific imagery, and print-proof previews may legitimately warrant quality 90+. Commercial requirements outrank a lab audit.
• The flagged asset is third-party. Ad creative, embedded map tiles, and chat widget avatars are outside your control. Note them and move on — or reconsider whether the third-party script is worth its weight.

Remember that Opportunities are advisory. A page can show this warning and still pass Core Web Vitals comfortably. Your goal is passing field metrics, not clearing every line item in a lab report.

---

8. Verifying the Fix

How to confirm it actually worked

1. Hard-reload the page with cache disabled (DevTools open, Network tab, "Disable cache" checked).
2. Filter the Network tab by Img and confirm the new file sizes are being served, not cached originals.
3. Re-run PageSpeed Insights on both mobile and desktop.
4. Check the LCP diagnostic — the render time of your LCP element should have dropped, often by 200–600 ms on mobile.
5. Wait 28 days before judging field data. Search Console's Core Web Vitals report uses a rolling 28-day window of real Chrome user data. Lab improvements show instantly; field improvements do not.

If the audit still fires after a correct re-encode, the usual culprits are: CDN cache not purged, a plugin re-processing your uploads and undoing your compression, or a theme serving a different image variant than the one you replaced.

---

9. Frequently Asked Questions

Does clearing this audit improve my rankings? Indirectly. The audit itself is not a ranking factor. But smaller images improve LCP, and LCP is a Core Web Vital that feeds Google's page experience signals. The route from compression to ranking runs through real-user load times, not through the Lighthouse report.

Why does the warning persist after I installed an optimization plugin? Many plugins optimize newly uploaded images only, or generate WebP copies while still serving the original in some templates. Check what's actually being requested in the Network tab rather than trusting the plugin's dashboard.

Should I just use quality 85 for everything? It's a strong default. Drop to 75 for thumbnails and listing grids where images render small, and raise it only for images where fine detail is the product.

My images are already WebP and it still fires. Then your WebP quality setting is too high — the audit applies the same logic. Re-export at 80–85.

Does the audit account for image dimensions? No. An oversized image compressed well can pass this audit while failing "Properly size images." They're independent problems and need independent fixes.

---

The Short Version

1. The audit means one thing: your images are encoded above quality 85.
2. Resize to displayed dimensions first, then re-encode at 80–85.
3. Prioritize the image identified as your LCP element — that's the one affecting a real metric.
4. Convert to WebP or AVIF in the same pass and clear two audits at once.
5. Purge your CDN cache, then re-test. Field data takes four weeks to catch up.

Fix the flagged files in seconds — compress them in your browser, no upload, no signup.