Lazy loading is one of the most effective WordPress performance techniques — and one of the easiest to misapply. Done right, it slashes initial page weight and speeds up load times. Done carelessly, it can hurt your Core Web Vitals and frustrate users. Knowing when lazy loading helps and when it hurts is what separates a faster site from a flickering one.
What Lazy Loading Actually Does
Lazy loading defers the loading of offscreen resources — images, iframes, sometimes videos — until the user scrolls near them. Instead of downloading every image the moment the page loads, the browser fetches them just in time. The payoff is a lighter initial load and faster first render.
When Lazy Loading Helps
- Long pages with many images, like galleries, archives, and image-heavy blog posts.
- Content far below the fold that many visitors never scroll to.
- Embedded media — YouTube iframes and maps that are expensive to load up front.
- Mobile users on slower connections, where saved bandwidth is most noticeable.
On these pages, lazy loading can dramatically cut the data downloaded before a user sees the content they came for.
When Lazy Loading Hurts
Above-the-Fold Images
Never lazy load images in the initial viewport — especially your hero image or LCP element. Deferring them delays the very content that Core Web Vitals measures, making your Largest Contentful Paint worse. Above-the-fold images should load eagerly.
Layout Shift
If lazy-loaded images do not reserve their space, content jumps as they pop in, hurting your Cumulative Layout Shift score. Always set width and height attributes (or an aspect-ratio) so the browser reserves room before the image arrives.
Native Lazy Loading in WordPress
Since WordPress 5.5, the loading=”lazy” attribute is added to images automatically. This native browser feature is lightweight and effective — no plugin required for most sites. Crucially, WordPress is smart enough to skip lazy loading on the first images in your content, protecting your LCP.
Going Beyond the Defaults
For finer control, performance plugins like WP Rocket or a dedicated lazy-load plugin can extend lazy loading to background images, iframes, and videos, and let you exclude specific images. Use the exclusion feature to keep your hero and logo loading eagerly while everything below the fold defers.
Test the Real Impact
Do not assume lazy loading helped — measure it. Run PageSpeed Insights and Lighthouse before and after, watching LCP and CLS specifically. The goal is a faster initial load without a slower LCP or a jumpy layout. If your LCP got worse, you probably lazy-loaded something above the fold.
Lazy Loading Iframes and Video
Images are not the only heavy offenders. Embedded YouTube players and Google Maps can each pull in hundreds of kilobytes of scripts before a user has even scrolled to them. Lazy loading these embeds — or replacing them with a lightweight click-to-load placeholder — often produces a bigger speed gain than optimizing a dozen images. The native loading attribute works on iframes too.
Combine Lazy Loading With Modern Formats
Lazy loading controls when an image loads; format and sizing control how heavy it is. For the biggest wins, pair lazy loading with WebP or AVIF images and properly sized responsive sources. A lazy-loaded, modern-format, correctly sized image is the trifecta of fast WordPress media.
Lazy load aggressively below the fold, never above it, always reserve space, and verify with real metrics. Applied with judgment, it is a genuine speed win — not a Core Web Vitals trap.
Frequently Asked Questions
Should I lazy load every image?
No. Lazy load images below the fold, but load above-the-fold images — especially your LCP element — eagerly. Lazy loading the hero image hurts Core Web Vitals.
Does WordPress lazy load images by default?
Yes, since version 5.5 WordPress adds loading=”lazy” automatically and intelligently skips the first images so your LCP is protected.