Image guides

Compare a Wide Web Image With a Mobile Variant

·

Prepare an image for the widths your layout actually uses. Comparing a wide version and a narrow version of the same source shows what file-size savings are available before you add them to responsive markup.

Compress Image for Web

Save a wide and a narrow copy

Load the 1,500 × 900 cedar cabin PNG or open the linked copy from disk. Select WebP, maximum width 1,280 px and a 200 KB target. Compress and save the resulting 1,280 × 768 image. Note its byte count or save the JSON byte report.

Choose maximum width 640 px and run the same source again, leaving the format and budget alone. The second output measures 640 × 384. Compare the cabin window and the smaller tree shapes at their intended display widths. Check the left edge in the preview to see the transparent strip.

Download the cedar cabin practice PNGOpen Compress Image for Web

Read the payload estimates

The reported bytes come from the saved file. At 10 Mbps, a 25,000-byte payload takes 20 ms at the stated steady rate. At 50 Mbps, the same payload takes 4 ms. Use the report to compare the two outputs under the same assumptions.

The estimates leave out latency, requests queued before the image, network overhead, image decoding and rendering. Check the actual image request in the published page before drawing conclusions about how quickly that page displays.

Open Compress Image for Webweb.dev image performance and responsive delivery

Choose the files to publish

Review the wider asset on high-density screens. Verify the browser selects the smaller asset on a narrow layout when you use a width-based srcset and a sizes value that describes the actual placement.

Select Original dimensions to compare encoders at the input resolution. WebP preserves transparency. JPEG fills the left strip with white and can be useful when the destination requires JPEG. If the output misses a strict byte limit, try a smaller width or lower the maximum quality and inspect the edges before using the replacement.

web.dev image performance and responsive delivery

Common questions

Does the payload estimate measure LCP?

It estimates how long the saved bytes take to transfer at a chosen fixed rate. LCP is an observation from the published page and includes the time until its largest visible element renders.

What happens to a source narrower than 640 pixels?

It stays at its original width and height. With a size target, the tool adjusts quality at that geometry.

Sources

Put it into practice.

Related guides