Image guides

Choose a Byte Budget for a PageSpeed Image

·

Use a saved image from a PageSpeed report to test a smaller file. Start with its displayed width and the devices that need to see it clearly. Set a byte budget you can check before replacing the image on the page.

Compress Image for Google PageSpeed

Run the content and avatar presets on the same file

Download the cedar cabin practice image or select Load example to open the same 1,500 × 900 PNG. Leave Content or blog image and WebP selected, and compress. The source is 18,251 bytes. The saved WebP measures 1,200 × 720 pixels. Look for Target met at 100,000 bytes, then compare the left edge and the cabin window in the two previews.

Change Image placement to Avatar or icon and compress again. Verify that the download is 200 × 120 pixels and compare its measured bytes to the 20,000-byte budget. The preset preserves the source ratio. Choose a square crop in your image editor if the avatar slot needs a square file.

Download the cedar cabin practice PNGOpen Compress Image for Google PageSpeed

Adjust the target without changing the page design

Set Custom width and target to choose your own maximum width and size. The encoder tries lower quality at the selected dimensions if the first attempt is above budget. When the best tested file still exceeds the limit, the result shows Target not reached. Lower the width only if the layout and device density allow it. Download original retains the selected file's bytes.

Choose WebP when the page can use it, especially for a file with transparent edges. JPEG fills transparent areas with white. You can inspect both versions and choose the one that fits the display and the budget. Canvas re-encoding can also produce a larger file than a compact original.

Chrome DevTools Improve image delivery insightOpen Compress Image for Google PageSpeed

Check the deployed page after replacing the file

Use the current image URL and the viewport where the opportunity was reported. After deployment, check which image the browser requested and whether the request serves the new file. Responsive markup can point different devices to different files. A good candidate for one display size may be too wide for another.

Rerun PageSpeed Insights on the actual page. Improve image delivery estimates potential savings using the downloaded file and its display context. A local byte target is a planning decision and cannot predict the page score or the report's findings.

Chrome DevTools Improve image delivery insight

Common questions

Does a 200 KB image pass PageSpeed Insights?

200 KB is a starting budget in the hero preset. PageSpeed Insights checks the delivered resource in the context of the page, including file format and displayed size.

Where can I check measured sizes later?

Download the byte report. It records source and output dimensions, encoded bytes, selected quality and the target for each saved result.

Sources

Put it into practice.

Related guides