How to fix Efficiently encode images in PageSpeed Insights
Updated

PageSpeed Insights flags Efficiently encode images when a JPEG, PNG, or WebP on your page could be smaller at similar visible quality. Download those files, re-encode them in the EditItAll compressor around quality 80, cap huge photos at 1920 or 1280 pixels, then replace the originals. The compressor runs in your browser - nothing is uploaded.
Do it now — free, in your browser
Open the JPEG compressorWhat the audit is actually measuring
Efficiently encode images is a compression check, not a layout check. PageSpeed Insights looks at each JPEG, PNG, and WebP on the page and estimates how many kilobytes you could drop by re-encoding at similar visible quality. It is not saying the photo is the wrong format, and it is not saying the pixels are too large - those are different audits (Serve images in next-gen formats and Properly size images).
The report names the files. You still have to fetch those originals from your site or CMS, re-encode them, and put the smaller copies back. EditItAll does not crawl your URL or talk to PageSpeed Insights. It just does the re-encode, in your browser.
Re-encode the files PageSpeed Insights named
Open the JPEG compressor (or the matching PNG / WebP tool if that is what the report listed) and drop the heavy originals in:
- Leave quality near 80 for photographs. That is usually indistinguishable on a screen and is the same band the JPEG quality guide recommends.
- If a photo is thousands of pixels wide but displays at a fraction of that, set max dimension to 1920 or 1280 - those are the real options on the compressor. Oversized pixels are the other half of page weight; see compress JPEG for the web.
- Read the in → out size in the results list. Too big? Drop quality about ten points and run again. There is no “compress to N KB” box - size is an output.
Export, download, replace the files on your server or in your CMS, then re-run PageSpeed Insights. Everything stayed on your device; you can go offline after the page loads. EXIF is stripped on export.
When the audit wants a different format instead
If the savings look small after a JPEG re-encode, PageSpeed Insights may also be asking for a modern format. WebP and AVIF usually beat JPEG at the same visible quality. Convert a copy with JPG to WebP or the WebP compressor and compare the listed sizes. Keep a JPEG fallback if you still serve older browsers.
PNG photos almost never belong on a web page. Convert those to JPG or WebP; lossless PNG recompress will not shrink a photograph much. The compressing images cluster covers the format choice in more depth.
What this will not fix
Re-encoding will not make a 4000-pixel hero fit an 800-pixel slot - that is Properly size images, and it needs a smaller pixel size. It will not lazy-load below-the-fold pictures, and it will not write srcset for you. EditItAll also cannot hit a kilobyte target automatically or remove JPEG artefacts that are already in the file. Compress once from the original, then stop.
Ready to try it?
Free, no sign-up, and nothing you open ever leaves your device.
Frequently asked questions
Does EditItAll connect to PageSpeed Insights?+
No. Download the files the report names, re-encode them here, and replace them on your site. Then re-run PageSpeed Insights yourself to see the new score.
What quality should I use to clear Efficiently encode images?+
For photographs, start near quality 80. If the listed output is still heavy, drop about ten points and preview. Below about 60, most photos look clearly worse.
Should I convert to WebP instead of compressing the JPEG?+
If page weight is the priority, try WebP or AVIF - they often win at the same look. That is a separate PageSpeed Insights audit (next-gen formats). JPEG is still the safest fallback.
Can I set a target size in KB to match the savings PageSpeed Insights estimated?+
No. There is no target-size field. Size is the output after you pick quality and max dimension. Aim a little under what the report suggested and re-check the live page.
Are the images uploaded while I compress them?+
No. Encoding runs in your browser. Files never leave your device, EXIF is stripped on export, and the tools keep working offline once the page has loaded.