How big should website images be?
Images are usually most of a page's weight, so they're the quickest win for speed. A 4,000 pixel phone photo shown 800 pixels wide downloads five times more than it needs to. Resize to roughly twice the size it appears (for sharp phone screens), save as WebP at around 75 to 80 quality, and most photos land well under 200 KB.
Which format?
The safe default for websites. Around 25 to 35% smaller than JPG at the same quality, supports transparency, and works in every current browser.
Smaller again, often half the size of JPG, but slower to make. Supported by all current browsers; WordPress has handled it since 6.5.
For email, documents and anywhere that might not read WebP. No transparency.
For screenshots, diagrams and graphics with sharp edges or transparency. Too heavy for photos.
Questions agencies ask
No. They're read, resized and re-saved by your browser on your own device. Nothing is sent to a server, so it's safe for client work and private photos, and it works offline once the page has loaded.
Yes. Re-saving an image keeps only the pixels, so EXIF data (GPS location, camera details, the date taken) is stripped. Photos are still turned the right way up first.
75 to 82 is the sweet spot for website photos: the files are a fraction of the size and the difference is very hard to see. Go higher for photography portfolios, lower for small thumbnails.
Images that were already well compressed, or PNG screenshots saved as PNG, sometimes can't be shrunk further. When that happens the tool keeps your original rather than give you a bigger file.
Yes. HEIC photos are converted as they're compressed, to JPG if you choose "Same format", since most websites can't show HEIC.
As many as your device's memory allows. A few hundred photos is fine on a laptop; they're processed two at a time.
A WordPress media library full of 5 MB photos?
Compressing new uploads is easy. Fixing the thousands already on a site, and the theme that serves full-size images everywhere, takes more care. I do that for agencies without breaking existing pages.
- White-label, under your brand, or alongside your team
- Laravel, WordPress, WooCommerce, integrations and tracking
- Inherited and half-finished sites taken over and stabilised
- UK based, straight to the developer, no account managers