A camera- or stock-library photo typically weighs 5-10x what your site actually needs. A quality-100 iPhone JPG is 4-8MB; the same image at quality 80 (visually identical) is 400-800KB. Without an optimization plugin, those originals pass straight through WordPress to every visitor - wasting bandwidth, lengthening loads, and damaging LCP.
Why this matters
One 2MB hero image can push LCP past 5 seconds on average mobile 4G. The same image at 300KB keeps LCP under the 2.5-second Core Web Vitals threshold. The difference is a "Good" versus "Poor" PageSpeed verdict, which feeds directly into Google rankings (Core Web Vitals has been a ranking signal since 2021).
Fewer bytes also mean lower CDN and storage bills - high-traffic sites save tens to hundreds of dollars per month. And there is the soft impact: a fast-loading page reads as "professional" while a sluggish one reads as "abandoned". Conversion analytics show this in real numbers.
How to detect
Run PageSpeed Insights on the homepage. The "Properly size images" and "Efficiently encode images" sections list every candidate with expected savings in KB. Totals above 500KB indicate high-leverage work.
Manual check: open Media Library, sort by file size. Anything over 500KB deserves attention. Anything over 1MB needs immediate fixing. Inspect pixel dimensions too: a 4000×3000 image displayed as 800×600 wastes resources - the server ships 12 megapixels and the browser scales to 0.5.
How to fix
Three complementary optimization layers:
Layer 1: lossy compression. Install Smush (free), Imagify (free + premium), or EWWW Image Optimizer (free, all local). Enable "Auto-optimize on upload" so every new image gets processed. Run "Bulk Optimize" on existing media - hours of work for libraries with thousands of files.
Layer 2: resizing. In Imagify or Settings > Media, set max width to 2000px. WordPress will downscale anything larger on upload. For body images, 1200-1600px is plenty.
Layer 3: modern format. WebP saves 25-35% over compressed JPG; AVIF saves another 40-50%. See the separate image_format_mix article.
Also enable lazy loading. WordPress 5.5+ does it automatically for content images, but some themes break the markup.
Common mistakes
Mistake one: setting quality too low (60 or below). Compression artifacts become visible in gradients and skin tones. 75-85 is the safe range. Mistake two: aggressive optimization with no backup of originals. If you want to move formats later, you only have the compressed file. Mistake three: optimizing without resizing. An 800×600 image at quality 60 weighs 30KB, but the same image at 4000×3000 at quality 60 still weighs 800KB. Resize first, compress second.
Verifying the fix
Re-run PageSpeed Insights. The "Properly size images" and "Efficiently encode images" warnings should be gone or near-zero. LCP should drop 300-1500ms depending on how heavy the original was. WebPageTest filmstrips should show content rendering noticeably sooner. Total bytes in DevTools Network should fall 30-60%. Lighthouse Performance score typically jumps 10-25 points.