Core Web Vitals: Check and Optimise Your Images
Large images can delay Largest Contentful Paint (LCP), but fonts, scripts and server response also matter. Inspect the measured LCP element before choosing a fix; it may be text rather than an image.
The numbers that matter
Google lists good Core Web Vitals as LCP within 2.5 seconds, Interaction to Next Paint within 200 milliseconds and Cumulative Layout Shift below 0.1. These are user-experience targets, not a promise of ranking gains. See Google’s Core Web Vitals guidance.
Two fixes, both free
First, resize an oversized source to suit its display size, allowing for high-density screens. Then compare compression settings with the image compressor. Try WebP with the image format converter, check small text and gradients, and retain the smallest acceptable result. Savings depend on the source.
Do it privately
The image tools process selected files in your browser. Page assets and optional measurement are separate from file processing; see the privacy policy. Keep the original and remeasure the published page after replacing its image.
Speed up your site free
Compress and convert images in your browser, no upload. Open the image compressor →
Frequently asked questions
What is a good LCP score?
Largest Contentful Paint of 2.5 seconds or less is considered good. Between 2.5 and 4 seconds needs improvement, and over 4 seconds is poor.
Should I use WebP or AVIF?
WebP and AVIF can reduce file size, but the best choice depends on the image, encoder settings and target browsers. Compare actual output rather than assuming one format is always smaller.
How do I compress images without losing quality?
Use a tool that reduces file size while keeping visual quality. The BeginThings image compressor does this in your browser with no upload.