How Image Optimization Affects Core Web Vitals
Images are the biggest cause of slow LCP scores. Here is how to fix them.
weFixPDF
The team behind weFixPDF — building free, no-signup PDF and image tools for everyday users and professionals.
Core Web Vitals measure how fast and stable your website feels to users. Images are the leading cause of poor scores. This guide walks you through exactly which image optimisations have the biggest impact on LCP, CLS, and your Google ranking.
What Are Core Web Vitals?
Core Web Vitals are a set of Google metrics that measure real user experience on your website. They directly influence your Google search ranking. The three metrics are:
- LCP (Largest Contentful Paint): How fast the main content loads. Target: under 2.5 seconds
- CLS (Cumulative Layout Shift): How stable the page is during load. Target: under 0.1
- FID / INP (Interaction to Next Paint): How responsive the page is to input. Target: under 200ms
Images affect all three.
How Images Impact LCP
The LCP element is often a hero image, a banner, or a large product photo. Every kilobyte you remove from that image directly reduces LCP time.
Action items:
- Convert all hero images from PNG or JPG to WebP using our PNG to WEBP converter
- Compress all images using our Image Compressor
- Serve correctly sized images — do not serve a 1920px image in a 400px container
- Preload your LCP image using
<link rel="preload">
How Images Impact CLS
When a browser loads an image without knowing its dimensions in advance, it inserts it suddenly — pushing other content down and causing a layout shift.
Fix: Always include width and height attributes on every <img> tag. Use CSS aspect-ratio for responsive images.
The Fastest Wins for Image Optimisation
| Action | Typical LCP Improvement |
|---|---|
| Convert JPG to WebP | 25–35% file size reduction |
| Compress PNG with weFixPDF | 40–70% file size reduction |
| Add lazy loading to off-screen images | Reduces initial page load |
| Serve next-gen formats | Passes Google PageSpeed audit |
Tools You Can Use Right Now
- PNG to WEBP — convert all site images to next-gen format
- Image Compressor — reduce file size without quality loss
Why Images Are the Primary Target for Web Performance
Images typically account for 50–80% of a web page's total download size. A page with 10 images at 1 MB each is 10 MB — this takes seconds to fully load on a mobile connection and will fail Google's Core Web Vitals thresholds.
Google measures page performance through three Core Web Vitals metrics. Two of them are directly affected by image optimization: Largest Contentful Paint (LCP) and Total Blocking Time (TBT through render blocking).
Largest Contentful Paint (LCP)
LCP measures how quickly the largest visible element on the page loads. This is almost always an image — the hero banner, the product photo, the featured image. Google's target: LCP under 2.5 seconds.
The fastest way to improve LCP: compress your above-the-fold images, serve them in WebP format, and preload the LCP image in your HTML head tag.
Practical reduction: converting a 400 KB JPG hero image to 120 KB WebP typically reduces LCP by 300–500ms on mobile connections.
Converting Images to WebP
WebP is 25–35% smaller than JPG at equivalent quality and 60–70% smaller than PNG. Browser support is universal (Chrome, Firefox, Edge, Safari 2020+).
For static images (uploaded once, served many times), converting to WebP before upload is the simplest approach. weFixPDF's PNG to WebP tool handles this conversion in the browser — your original files are never uploaded to a server.
Correct Image Dimensions
Serving a 2000×1500 pixel image in a 400×300 container wastes 25× the download size. Always resize images to the actual display dimensions before uploading.
On most websites, hero images need to be at most 1920px wide. Blog thumbnails are typically 600–800px. Product images on e-commerce sites: 800–1200px. Anything larger is serving pixels nobody will ever see.
Lazy Loading
Images below the fold (not visible in the initial viewport) don't need to load immediately. The loading="lazy" HTML attribute defers their loading until the user scrolls near them:
(html example)
<img src="image.webp" loading="lazy" alt="Description" width="800" height="600">
(end example)
This significantly reduces initial page weight and improves perceived performance.
The width and height Attributes
Always specify explicit width and height on img elements elements. This prevents layout shift (Cumulative Layout Shift — another Core Web Vital) as images load, because the browser reserves the correct space in advance.
Practical Checklist
- Convert all images to WebP (with JPG/PNG fallback for older browsers)
- Resize images to actual display dimensions
- Compress images to under 200 KB for web use
- Add loading="lazy" to images below the fold
- Add explicit width and height attributes
- Preload the LCP image with the preload link tag
Key Takeaways
Get started free
Convert to WebP Free Now
No sign-up. No watermarks. Files deleted immediately.
Convert to WebP Free NowFrequently Asked Questions
What image format is best for Core Web Vitals?
How much does image compression actually improve LCP?
Does image size affect CLS?
What is lazy loading and should I use it?
Related Guides
BlogUse Cases
WorkflowsCompare & Learn
vs OthersTry These Tools