OOmnistu

Blog / Web & Ecommerce

Web & Ecommerce

Lazy-loading images without delaying your main content

Use native image lazy loading below the first screen, reserve image space and avoid delaying the image that matters for LCP.

OOmnistu
Reviewed 2026-11-16 · 4 min read

Lazy loading defers an image until it approaches the visible part of a page. It can avoid fetching distant images immediately, but it is the wrong default for an image a visitor needs to see at once. The main rule is simple: leave first-screen images, especially a likely Largest Contentful Paint image, on normal eager loading. Consider lazy loading for images farther down the page.

Google's browser-level lazy-loading guide explains the native loading attribute. You do not need a separate JavaScript library merely to use that browser feature.

What loading="lazy" actually changes

The attribute asks the browser to defer an image until it reaches a calculated distance from the viewport. It does not mean "wait until the image is already visible," and it does not give the developer an exact universal scroll distance.

The default eager behaviour loads the image normally. Explicitly setting loading="eager" can be useful when a theme or plugin would otherwise add lazy loading automatically. It does not, by itself, give the image a higher fetch priority than an ordinary image without the attribute.

Different page layouts and devices expose different content in the first screen. An image below the fold on one phone may be visible immediately on a large monitor. Decide by inspecting the actual layout rather than marking images lazy solely because they are the second or third image in the source file.

A small example

These are illustrative HTML patterns. The filenames refer to example project assets, not supplied downloads.

<!-- Main image visible when the page opens: normal loading -->
<img src="article-main.jpg"
     alt="A developer reviewing a page performance report"
     width="1200" height="675">

<!-- Supporting image farther down the article -->
<img src="report-detail.jpg"
     alt="Detail of the report's layout shift diagnostics"
     width="960" height="540"
     loading="lazy">

The loading decision and reserved space are separate. Both images declare dimensions so the browser can reserve the correct proportions while the files load. The surrounding responsive design still needs to display them appropriately at narrower widths.

Use descriptions that match the actual image when implementing this pattern. Do not copy the example alt text onto an unrelated asset.

Do not lazy-load the image you need first

Core Web Vitals includes LCP, a loading-performance metric. If a prominent image is the measured LCP element, delaying its request can work against the experience you are trying to improve.

A common mistake is a global plugin setting that marks every image lazy, including the article's main image. Review the generated HTML as well as the content editor's settings: the final template may add attributes the author never entered.

Fetch priority is a different control. The lazy-loading guide describes fetchpriority="high" for an important image, but combining it with lazy loading does not cancel the deferral while the image is off-screen. Do not add both attributes as a generic "make it fast" recipe.

Reserve space to reduce layout shifts

When an image arrives without reserved space, it can push text and controls out of position. Google recommends width and height attributes, or an appropriate sizing approach, so the browser knows the space to allocate.

This matters for lazy-loaded content because the reader may already be near the image when it loads. In some gallery layouts, missing dimensions can also cause images to occupy no space initially, undermining the expected deferral behaviour.

Google's business-owner performance guide discusses reserved space for lazy-loaded images and advertisements. For a monetized blog, treat both as layout decisions: readers should not lose their place when another element appears.

Native lazy loading has a defined scope

For responsive images using a picture element, put loading on its fallback img element. The attribute does not apply directly to CSS background images.

Browsers that do not support the attribute can ignore it and load the image normally. If the project has special compatibility needs or already uses a lazy-loading library, review the interaction rather than layering a second system on top without testing.

This guide does not prescribe exact browser thresholds, legacy-browser libraries or a carousel strategy. Those depend on the implementation and deserve their own checks.

A practical test before release

Use this suggested checklist:

  1. Inspect the page at mobile and desktop sizes and identify which images are initially visible.
  2. Confirm that the important first-screen image is not accidentally lazy-loaded.
  3. Check that supporting images below the first screen use the intended loading behaviour.
  4. Scroll through the whole page and watch for missing images or text moving unexpectedly.
  5. Inspect network and performance diagnostics under representative conditions.
  6. Compare loading and stability before and after; do not assume the attribute alone improved them.

Lazy loading is one part of image delivery. Image dimensions, file size and the page's broader loading sequence still matter. No fixed speed-up or Core Web Vitals improvement is promised by adding an attribute.

By Omnistu. Technical guidance reviewed 16 November 2026. HTML examples are illustrative; they have not been tested in your site's template.

Sources

Previous
Improving INP: why a page feels slow to respond, and where to look