WordPress Lazy Loading: What to Lazy Load and What Never to Delay

Lazy loading can make a WordPress page lighter at the start by delaying images and iframes that are not yet on screen. Used well, it saves bandwidth and reduces work during the first part of a page load. Used badly, it can delay the very image the visitor is waiting to see.

The main rule is simple: lazy-load media that starts below the first screen, but do not blindly lazy-load the image that becomes Largest Contentful Paint. Before changing anything, learn how to test WordPress speed so you can compare the same page before and after the change.

What lazy loading actually does

An image with loading="lazy" tells a supporting browser that it does not need to fetch the file right away if the image is far enough from the current viewport. The browser decides when the image is close enough to request. This can reduce the number of early network requests on long articles, galleries, product archives, and other image-heavy pages.

WordPress has native logic for image loading attributes. Modern WordPress can add lazy loading where it makes sense and can also add other loading hints, such as fetchpriority="high" for an important image. WordPress core also avoids combining a high fetch priority with lazy loading on the same image because those signals point in opposite directions.

That means a separate lazy-load plugin is not automatically needed. A plugin may still add value when it handles background images, videos, iframes, special galleries, or older custom markup, but you should first see what WordPress and the browser are already doing.

Do not lazy-load the LCP image

The image that controls LCP is often a hero photo, featured image, banner, or large product image near the top of the page. If that image is marked lazy, the browser may wait before requesting it. That can turn a normal image download into a late image download.

First identify the actual LCP element in Lighthouse or PageSpeed Insights. Then view the page source or inspect the element. If the LCP image has loading="lazy", remove that behavior for the important image. Our guide on improving WordPress LCP explains the rest of the chain, including discovery time, image size, server response, and render delay.

Do not assume the first image in the HTML is always the LCP image. A cookie banner, heading, background image, slider, or responsive layout can change which element becomes largest in the first viewport. Test the real page at the screen size that matters.

Good candidates for lazy loading

Images far below the fold are the clearest candidates. Think of screenshots in the middle of a tutorial, photos near the bottom of a long article, related-post thumbnails, footer logos, and images in collapsed sections that are not visible at first.

Embedded iframes can also be heavy. A video player, map, or social embed may load JavaScript and network requests before the visitor reaches it. Native iframe lazy loading can delay some of that work. This is especially useful on pages with several embeds.

Lazy loading is not a reason to keep oversized media. A 3000-pixel image is still too large if it is displayed at 700 pixels. Combine lazy loading with proper WordPress image optimization and responsive image markup.

Images that should usually load early

The main hero or featured image should usually load early when it is visible as soon as the page opens. The same applies to a logo if it is large enough to matter, an above-the-fold product image, or another image that users must see before they can understand the page.

An image can also deserve early loading when it appears immediately after a short title on small screens. Desktop and mobile layouts can place the same image in different positions, so test both. A setting that looks safe on a wide monitor may delay an image that sits in the first mobile viewport.

Be careful with sliders and carousels. The first slide may be important, while later slides can often wait. A tool that lazy-loads every slide the same way may delay the first one or preload too many hidden images. The right rule depends on what the visitor sees first.

Check for duplicate lazy-loading systems

Problems often appear when WordPress core, an optimization plugin, a theme, and a CDN all try to rewrite the same image markup. One system may replace image URLs with data attributes. Another may add native loading="lazy". A third may inject JavaScript that waits for an intersection observer.

Use one clear owner where possible. View the final HTML in the browser, not just the editor markup. If the page contains several layers of lazy-load attributes and scripts, turn off the extras and retest. This follows the same rule used for WordPress caching layers: overlapping tools make problems harder to trace.

Background images need special care

CSS background images do not use the normal img loading attribute. Page builders often use a background image for a hero section because it is convenient for design. The browser may discover that file later than it would discover an ordinary image in the HTML.

If a background image is the LCP element, consider whether it should be a real responsive image instead. If the design must use CSS, make sure the file is not hidden behind a large stylesheet that arrives late. Preloading can help in some cases, but do not preload every background image on the page.

The goal is not to add more hints. The goal is to make the important resource easy for the browser to discover and delay the resources that truly can wait.

Lazy loading and responsive images work together

Lazy loading answers when an image should be requested. Responsive images help answer which file should be requested. These are different jobs.

WordPress normally creates several image sizes and can output srcset and sizes. The browser then chooses a suitable candidate. If the sizes value is wrong, a lazy-loaded image can still be much larger than needed. Read our responsive images guide if mobile visitors are still downloading large files.

Do not judge lazy loading by request count alone

A waterfall may show fewer requests at the start after lazy loading is enabled. That is useful, but the visitor experience matters more. Check LCP, page responsiveness, scroll behavior, and whether images appear in time as the user moves down the page.

A very aggressive script can create visible blank boxes while the reader scrolls. On a fast desktop connection this may be hard to notice. On a slower phone it can be obvious. Native browser lazy loading is often a good starting point because the browser controls how early to fetch the image.

How to test a WordPress lazy-loading setup

  1. Choose a page with an above-the-fold image and several images farther down.
  2. Run a Lighthouse or PageSpeed test and identify the LCP element.
  3. Inspect the LCP image and confirm it is not being delayed by lazy loading.
  4. Scroll the page slowly on a phone and watch whether later images appear before the reader reaches them.
  5. Check the Network panel to see when below-the-fold images are requested.
  6. Test with cache enabled because production behavior can differ from an uncached admin session.

If the page uses ads, video, or other outside tools, also review third-party JavaScript cost. Delaying an image will not solve a page that is busy running outside scripts.

When a lazy-load plugin can still help

A plugin can be useful if your site has image markup that WordPress does not control, CSS background images that need a special strategy, complex galleries, video facade features, or a CDN workflow that needs URL rewriting. The plugin should solve a specific gap rather than duplicate what the browser already does.

After installing one, check the HTML and waterfall again. If it adds a large JavaScript file to save a few small image requests, the trade may not be worth it. If it delays a heavy video embed until the visitor approaches it, the trade can be very good.

A safe rule for most sites

Keep the first important image eager and easy to discover. Lazy-load media that starts below the fold. Keep image dimensions in the markup so space can be reserved. Use responsive sizes so mobile devices receive smaller files. Then measure the page again.

That gives you the main benefit of lazy loading without treating every image as if it has the same job.

Sources and further reading

Related FastWP guides