Why Images Are the Biggest Cause of a Slow Page

On a typical page, images are 60 to 80 percent of the transferred bytes. That single fact explains most slow pages: the HTML is small, the CSS is small, and then there is a 4 MB photograph.

Bytes become seconds on a mobile connection

On a 4G connection a 4 MB image takes several seconds to download, and the visitor stares at a blank space the whole time. On a slower connection or a poor signal it can take ten. Compression and resizing attack this directly.

Layout shift is worse than the delay

An image without declared dimensions reflows the page when it finally arrives, pushing the text the visitor was reading further down. That is measured as Cumulative Layout Shift and it is one of the worst experiences on the web. Always reserve the space with width and height attributes.

Which fixes pay off, in order

First, never serve more pixels than are displayed. Second, choose the right format. Third, compress. Fourth, lazy-load images below the fold so they do not compete with the ones the visitor is looking at. Each step is cheaper to implement than the one after it, and each produces a smaller file.

What good looks like

A 1440px-wide photograph, correctly resized and compressed at 0.80 in WebP, is typically 80–150 KB. The same photograph straight off a phone camera is 3–5 MB. That is a twenty- to thirty-fold difference for an image most visitors could not tell apart.

Compress an image now — free and private

← All image guides