Image Tools · Use case

Image Compressor for web pages

compress images for a website so pages hit Core Web Vitals targets and pass PageSpeed audits.

Images are the single largest contributor to slow Largest Contentful Paint scores. A 2 MB hero image can push LCP past 4 seconds on 3G — and that's the threshold where Google flags your page as 'poor' in Core Web Vitals.

Image Compressor drops image weight 60–80% without visible quality loss. Combine it with the right format (WebP or AVIF) and you can shave seconds off page load.

How to use Image Compressor for web pages

  1. Open Image Compressor and drop the image you're about to publish.
  2. Convert to WebP for photos or PNG-8 for icons and flat graphics using Image Converter.
  3. Compress at 75–80% quality for hero images, 65% for below-the-fold thumbnails.
  4. Upload the compressed asset to your CMS or CDN.

Tips that actually matter for this case

  • Aim for hero images under 200 KB and thumbnails under 30 KB. Anything larger will show up as an LCP issue in PageSpeed.
  • Serve different sizes with a responsive <img srcset> — you don't need to send desktop-resolution images to phones.
  • If your CDN supports on-the-fly compression, still pre-compress locally. Layered compression is fine; huge originals are not.

Frequently asked questions

What is a good image size for a website?+

Hero images: under 200 KB. Thumbnails: under 30 KB. Full-width photos: under 500 KB. Above those thresholds and Core Web Vitals will start to complain.

Should I use WebP or JPEG for web images?+

WebP for photos — it compresses 25–35% smaller than JPEG at equivalent quality. JPEG is still fine as a fallback for older browsers, but every modern browser has supported WebP since 2020.

Other ways to use Image Compressor

More image tools for this workflow