SquishPixel Blog · Image optimisation · Image formats · Core Web Vitals

Progressive image loading: three layers for image-heavy landing pages

According to DEV Community, a landing page with twenty high-resolution images above the fold can take 8 seconds to load on a 4G connection, while users leave after about 3. The article says the answer is not fewer images but smarter loading.

The piece splits the approach into three layers. The first is an inline placeholder: a tiny SVG, described as 20 bytes, that holds the image's dominant colour and is embedded directly in the src attribute as a data URI. Because it is part of the page itself, it costs no network request.

The second layer is a low-quality image, a blurred JPEG of about 1KB served through srcset (the HTML attribute that lets the browser pick from several image sizes) at a very small width. The article says it appears in roughly 200 milliseconds. The third layer is the full image, loaded with loading="lazy" and with fetchpriority set according to where the image sits in the viewport.

On Largest Contentful Paint (LCP), the time at which the biggest visible element finishes rendering, the article says the LCP image should not be lazy-loaded. It should instead get fetchpriority="high" and be preloaded. It also says visually driven sites need an LCP under 2 seconds, and that the swap from placeholder to full image should go unnoticed.

For formats, DEV Community recommends AVIF where supported, which it says is 40% smaller than WebP. WebP is the fallback, and JPEG the final fallback, all delivered through the picture element. Its closing point is that progressive loading is three separate problems, to be solved one layer at a time.

Why it matters

Slow image loading is a common reason visitors leave a landing page. The article's main idea is that you do not have to strip out imagery to fix this. You can change when and how each image arrives, so something useful shows up almost immediately.

The advice on the LCP image is easy to get wrong. Lazy-loading every image is a popular habit, but the article says the main above-the-fold image should be treated differently and loaded early. Format choice matters too, since smaller files help every layer. Treat the specific figures as the author's claims, and test them on your own pages.

Source: DEV Community. This brief summarises their reporting; read the original for the full detail.