Meregate.com
Monday, November 16, 2026
Home โ€บ SEO โ€บ What Is Lazy Loading? Images, Speed & Core Web Vitals (2026)

What Is Lazy Loading? Images, Speed & Core Web Vitals (2026)

What Is Lazy Loading? Images, Speed & Core Web Vitals (2026)

Lazy loading is a simple idea: the browser only downloads an image when a visitor is about to see it. Images further down the page wait. They load as the visitor scrolls, instead of all at once when the page first opens.

That one change can make a real difference. On a long blog post or product page with 20 images, a visitor who only reads the first screen may never need 15 of them. Without lazy loading, the browser still downloads all 20 before the page feels ready.

This guide explains what lazy loading is, how browsers do it, how to turn it on, and the one mistake that can make your site slower instead of faster.

Last updated: November 2026

What is lazy loading?

Lazy loading is a performance technique that puts off loading images, videos, and iframes until they are needed. The word “lazy” fits: the browser avoids work for as long as it can.

By default, a browser downloads every image on a page as soon as it reads the HTML โ€” even the ones at the bottom of a 3,000-word article. That is called eager loading, and it is how the web worked for years.

Lazy loading flips that order. The browser only downloads the images near the top, the part a visitor can see without scrolling. Everything below the fold waits until the visitor scrolls close to it.

The technique is not limited to images. Videos, embedded maps, and iframes can be lazy-loaded too. But images are the most common case, and they carry the most weight โ€” a 2024 HTTP Archive study found that images make up roughly 45% of the total weight of an average web page. Holding back images you do not need yet is often the biggest single speed win on a page.

Why lazy loading matters

Lazy loading helps in three clear ways.

1. Faster first load

When the browser skips a dozen below-the-fold images, the page becomes usable sooner. The text, the layout, and the first images show up faster. Google’s Chrome team found in a 2019 study that images below the fold were responsible for 30 to 50 percent of the initial bandwidth on a typical web page.

2. Less data for your visitors

Many visitors never scroll to the bottom. On a phone, a reader may read the first two paragraphs and leave. Without lazy loading, that visitor already paid for every image on the page in mobile data. With it, they only download what they actually saw.

3. Less work for your server

Every image request hits your server or your image host. When half the images on a page never get requested, your server handles fewer requests. On a busy site, that adds up to real savings in bandwidth and server load.

How lazy loading works in the browser

Modern browsers handle lazy loading on their own. You add one small attribute to an image tag, and the browser takes care of the rest:

<img src="product-photo.jpg" alt="Blue running shoes on a white background" width="800" height="600" loading="lazy">

That loading="lazy" attribute is a hint to the browser. It says: do not fetch this image yet. Wait until the image is close to the visible part of the page, then fetch it.

The browser does not wait until the image is actually on screen. That would be too late โ€” the visitor would see a blank space while the file downloads. Instead, the browser starts fetching a little early. In Chrome, a lazy image starts loading when it comes within about 1,250 pixels of the viewport on a fast connection, and within about 2,500 pixels on a slow connection like 3G.

A screenshot of the GSS Data Explorer website homepage
Source: Wikimedia Commons

The loading attribute takes three values: lazy (wait until the image is near the viewport), eager (load it right away โ€” the default), and auto (let the browser decide).

Before this attribute existed, developers had to write JavaScript to get the same result, usually with the Intersection Observer API: a script watched each image and swapped the real image address into place when it came near the viewport. That still works and gives you more control โ€” for example, you can set your own distance or add a fade-in effect. But for most sites, the built-in attribute is enough, and it needs no JavaScript at all.

Which browsers support it?

Native lazy loading works in all major browsers today. Support started in Chrome 77 (September 2019), Edge 79, Firefox 75, and Safari 15.4. Older browsers simply ignore the attribute and load the image normally, so nothing breaks.

Lazy loading in WordPress: it is already on

If your site runs on WordPress, you may already have lazy loading and not know it. WordPress has added loading="lazy" to images by default since version 5.5, released in August 2020. Any image you add through the Media Library or the block editor gets the attribute automatically, as long as it has width and height values โ€” which WordPress fills in for you.

WordPress has also learned to protect your most important image. Since version 5.9, it skips lazy loading for the first image in your content, which is often the featured image. Since version 6.3, it skips the first three content images and adds fetchpriority="high" to the first large image โ€” the one most likely to be your Largest Contentful Paint element.

You can check whether it is working on your own site. Open any post, right-click an image below the fold, and choose “Inspect.” Look for loading="lazy" in the img tag.

One warning: themes, page builders, and optimization plugins can override what WordPress does. A plugin might add lazy loading to your hero image, or a theme might hard-code images without the attribute.

If you want lazy loading for things WordPress does not cover โ€” CSS background images, for example โ€” a plugin can help. Popular performance plugins such as WP Rocket and Optimole add lazy loading for background images, iframes, and videos.

When NOT to lazy-load an image

This is the most important part of this guide. Lazy loading helps below-the-fold images. It hurts images at the top of the page.

The image a visitor sees first โ€” usually the hero image or the featured image โ€” is often the Largest Contentful Paint (LCP) element. LCP is the time it takes for the biggest visible piece of content to appear, and Google counts it as one of the three Core Web Vitals. Google’s guidance says LCP should happen within 2.5 seconds.

So the rule is simple: never lazy-load the first image on the page. Use loading="eager" on it, or leave the attribute off entirely, since eager is the default. WordPress already skips the first three images for you, but if you add images by hand or use a plugin, check that the top image is not lazy-loaded.

The same rule applies to any image that is visible when the page first opens: your logo, a product photo above the fold, or the main image on a landing page. If a visitor can see it without scrolling, load it right away.

Images inside hidden areas need care too. An image inside a tab that starts closed, or a slide in a carousel that is not showing, will not load until that tab or slide opens. That is usually fine โ€” but if the hidden content matters for search, keep reading, because Google treats it differently.

How lazy loading helps your Core Web Vitals

Core Web Vitals are three numbers Google uses as part of its page experience signals: Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP). Lazy loading touches all three.

Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible element to show up. Lazy loading helps LCP in an indirect way: by holding back off-screen images, it frees up bandwidth and browser attention for the content at the top. But remember the warning above โ€” lazy-loading the LCP image itself does the opposite. In real-world tests, lazy-loading a hero image typically adds 300 to 500 milliseconds to LCP, a big chunk of a 2.5-second budget.

A screenshot of the Midori web browser open on a computer screen
Source: Wikimedia Commons

Cumulative Layout Shift (CLS)

CLS measures how much a page jumps around while it loads. Lazy loading can make CLS worse if you are not careful. When the browser has not downloaded an image yet, it does not know how big the image is. If you give it no size information, it reserves no space. Then, when the image finally loads as the visitor scrolls, the page suddenly grows taller and everything below it jumps down. That jump is layout shift, and visitors hate it โ€” especially when they are about to tap a link and the page moves under their finger.

The fix is easy: always set width and height on every image, lazy or not. With those numbers, the browser reserves the right amount of space before the image arrives, and nothing moves. You can also use the CSS aspect-ratio property to do the same job. WordPress adds width and height to Media Library images by default, which is one reason its built-in lazy loading works well.

Interaction to Next Paint (INP)

INP measures how quickly a page responds when a visitor clicks or taps. A browser busy downloading 20 images has less room to handle a click, so fewer downloads during the first load means a more responsive page.

Lazy loading and SEO: what Google actually sees

A common worry is that lazy-loaded images might hurt search rankings because Google cannot see them. The short answer: native lazy loading is safe for SEO. JavaScript-only lazy loading can be risky. The difference matters.

Googlebot, the crawler that reads your pages, does not scroll the way a person does. Google’s own guidance says its recommended lazy-loading methods should not depend on a user scrolling or clicking, because Google Search does not interact with your page.

That is why the native loading="lazy" attribute is the safe choice. The image address stays in the normal src attribute in the HTML, so Googlebot can find it even though the browser holds back the download.

The risky setup is the old pattern where the real image address sits in a data-src attribute and only moves into src when a visitor scrolls. If Googlebot never triggers that scroll, it may never see the image.

A few practical rules keep your images visible to Google:

  • Use the native attribute. Keep the real image address in src, not hidden in a data attribute.
  • Write good alt text. Google uses alt text to understand what an image shows. Our guide to what alt text is and how to write it covers this in detail.
  • Do not hide images behind clicks. If an image only appears after a visitor clicks something, Google may never find it.
  • Check with Search Console. Use the URL Inspection tool and look at the rendered HTML. Your image addresses should appear in src attributes there.

Lazy loading vs. other image speed fixes

Lazy loading is one tool, not the whole fix. It decides when an image downloads, but it does nothing about how big the file is โ€” a 2 MB photo still takes a long time to download when its turn comes. That is why compressing your images for the web matters just as much. A clear file name helps too: our guide to image file names for SEO explains the naming rules that work. Each step helps, and none of them replaces the others.

How to test lazy loading on your site

You do not need a developer to check whether lazy loading is working. Here are four quick checks.

1. View the page source

Open a long page on your site, right-click, and choose “View page source.” Search for loading="lazy". You should see it on images below the fold, and not on the first image.

2. Watch the network tab

In Chrome, open DevTools (F12), go to the Network tab, and reload the page without scrolling. You should see only the top images downloading. Now scroll down slowly โ€” new image requests should appear as each section comes into view.

3. Run PageSpeed Insights

Google’s PageSpeed Insights tool flags images that should be lazy-loaded โ€” and, just as useful, images that are lazy-loaded but should not be. Look for the “Largest Contentful Paint image was lazily loaded” warning.

4. Check the rendered HTML in Search Console

In Google Search Console, use the URL Inspection tool and open the rendered HTML. Confirm that your lazy-loaded images appear with their addresses in src attributes. If they do, Googlebot can find them.

Frequently asked questions

Does lazy loading hurt SEO?

No โ€” not when you use the browser’s built-in loading="lazy" attribute. The image address stays in the src attribute, so Googlebot can find it. The risk only appears with JavaScript setups that hide the image address until a visitor scrolls, because Googlebot does not scroll.

Is lazy loading good for SEO?

It helps indirectly. Lazy loading improves page speed and Core Web Vitals, which are part of Google’s page experience signals. But lazy loading alone will not rank a page โ€” the content, the keywords, and the links still matter more.

Does WordPress lazy load images automatically?

Yes. Since WordPress 5.5, images added through the Media Library get loading="lazy" automatically. Since WordPress 6.3, the first three content images skip lazy loading and the first large image gets fetchpriority="high".

Should I lazy load all images?

No. Lazy-load the images below the fold only. The hero image, the logo, and any image visible when the page first opens should load right away. Lazy-loading those makes the page slower, not faster.

What is the difference between lazy loading and eager loading?

Eager loading means the browser downloads the image as soon as it reads the page โ€” that is the default. Lazy loading means the browser waits until the image is close to the visible area. Eager is right for the first screen; lazy is right for everything below it.

Can lazy loading break images?

It should not, if you use the native attribute. Old browsers ignore loading="lazy" and load the image normally. Problems usually come from plugins or custom JavaScript that conflict with the native behavior. If images fail to appear, check for a plugin conflict first.

The bottom line

Lazy loading is one of the simplest speed wins on the web. One attribute โ€” loading="lazy" โ€” tells the browser to hold back off-screen images until a visitor is about to see them. The page loads faster, visitors on mobile save data, and your server does less work.

On WordPress, most of this already happens for you. Since version 5.5, WordPress adds lazy loading to your images, and since version 6.3 it protects the first few images so your top content still loads fast.

The only rule you need to remember: lazy-load the images below the fold, never the one at the top. Get that right, give every image its width and height, and keep the real image address in src so Google can find it.

If you are working through image SEO step by step, the next piece of the puzzle is how Google finds your images in the first place. Our guide to what an image sitemap is explains how a sitemap helps search engines discover the images on your site.

Taylor Orlando

Taylor Orlando is a content writer at Meregate covering websites, SEO, and AI. Taylor breaks down complex topics into simple, practical guides that help small businesses build better websites, rank higher on Google, and get real value from AI tools โ€” no jargon, no fluff.

Related Articles

Ubersuggest vs Moz: Which SEO Tool Wins in 2026?
SEO

Ubersuggest vs Moz: Which SEO Tool Wins in 2026?

Ubersuggest and Moz both cover keyword research, site audits and backlinks, but they serve different buyers. We compare their prices, data and limits so you can pick the right one.

November 16, 2026 ยท Taylor Orlando
What Is DNS? How the Domain Name System Works (2026)
SEO

What Is DNS? How the Domain Name System Works (2026)

DNS is the system that turns a domain name you type into the IP address of the server that holds the website. This guide explains how a lookup works, the four servers involved, and the DNS records every website owner should know.

November 16, 2026 ยท Taylor Orlando