Are images really the main bottleneck killing your site's performance?

Martin Splitt highlights a field reality that many SEOs know all too well: images are heavy, often far heavier than HTML, CSS, and JavaScript combined. On most sites, they account for 50 to 70% of a page's total weight.

This statement reflects Google's continued emphasis on Core Web Vitals, particularly LCP (Largest Contentful Paint) and CLS (Cumulative Layout Shift). An unoptimized image delays the display of main content, degrades user experience, and can cause your rankings to plummet.

Why do unoptimized images slow down pages so much?

Unoptimized images create multiple problems: excessive file size (poorly compressed JPEG or PNG files), unsuitable formats (no WebP or AVIF support), dimensions too large for actual display, and synchronous loading that blocks rendering.

Every extra second of delay increases bounce rate and deteriorates the user signals Google monitors. It's a vicious cycle: slowdown → poor UX → worse rankings.

What does Google mean by the "cost in time and money"?

The time cost is users who abandon before the page even loads. The money cost is wasted bandwidth: serving 2 MB images when 200 KB would suffice multiplies hosting and CDN costs.

For a high-traffic site, savings from image optimization can amount to thousands of euros annually. Not to mention the direct impact on conversions.

Does this statement apply to all types of websites?

Obviously, a text blog will have fewer issues than an e-commerce site filled with product visuals. But even a "light" site can suffer from a poorly optimized hero image at the top of the page, delaying everything else.

Editorial sites, portfolios, and e-commerce product pages are most exposed. For them, image management isn't a technical detail — it's a strategic priority.

• Images often represent 50 to 70% of a webpage's total weight
• They directly impact LCP and CLS (Core Web Vitals)
• An unoptimized image increases bounce rate and degrades user experience
• Hidden costs: bandwidth, hosting, CDN
• All sites are affected, but e-commerce and portfolio sites are most vulnerable

Is this statement consistent with real-world practices?

Absolutely. Technical SEO audits consistently reveal the same problem: poorly compressed images, served in outdated formats, and without lazy loading. It's a classic issue.

In practice? WordPress sites with full-format JPEG uploads (3000x2000 px) when the actual display is 800x600. CMSs that don't auto-generate WebP versions. Developers embedding PNGs for photos when that format is meant for graphics.

What nuances should be added to this statement?

Google doesn't specify a precise threshold. What image weight becomes "problematic"? It depends on context: content type, audience (mobile vs desktop), average visitor connection quality.

[To verify]: Google doesn't explicitly state that reducing image weight directly improves rankings. What's certain is that it improves Core Web Vitals, which do influence ranking. The causality chain is indirect but real.

In what cases doesn't this rule really apply?

If your site is a pure SaaS application with minimal visual content, or a minimalist institutional site, images won't be your main bottleneck. Heavy JavaScript, multiple requests, and unoptimized fonts will take over.

But let's be honest: these cases are rare. Most modern websites are drowning in images, often due to poorly configured CMSs or contributors who don't think about performance.

What concrete steps should you take to optimize images?

First step: audit your current state. PageSpeed Insights, WebPageTest, or Lighthouse show you exactly which images are problematic and how many kilobytes can be saved.

Then act on three levers: compression (reduce file size without losing too much quality), format (switch to WebP or AVIF when supported), and loading (lazy loading, dimensions adapted to viewport).

What mistakes should you absolutely avoid?

Don't skip compressing images before upload. Don't serve the same 4000 px image to mobile devices. Don't forget width and height attributes, which cause CLS when the image loads.

Another common mistake: thinking your CDN will fix everything. A CDN speeds up delivery, but if an image weighs 3 MB, it still weighs 3 MB—just delivered faster. Optimize first, distribute second.

How can you verify your site meets best practices?

Use standard tools: Google PageSpeed Insights, GTmetrix, WebPageTest. They identify unoptimized images and calculate potential savings.

Also test on mobile with simulated 3G connection (throttling in Chrome DevTools). If your images take 5 seconds to display, it's dead for UX—and Google knows it.

• Audit all pages with PageSpeed Insights or Lighthouse
• Convert JPEGs/PNGs to WebP or AVIF (with fallback)
• Compress images using tools like TinyPNG, ImageOptim, or Squoosh
• Implement native lazy loading (loading="lazy")
• Define width and height attributes to prevent CLS
• Use responsive images with srcset and sizes
• Enable Brotli or Gzip compression server-side
• Configure browser cache for static images (1 year minimum)