Skip to content

Technical SEO

Lazy Loading: When It Helps Speed and When It Hurts SEO

By Shayan Ahmad · · 7 min read

Lazy Loading: When It Helps Speed and When It Hurts SEO (WhiteLinko blog banner)

Lazy-loading is one of the easiest speed wins on a long page, and one of the easiest ways to make a first impression worse. Used on the right images, it stops the browser downloading a long grid of photos that the visitor has not reached yet. Used on the wrong one, it delays the hero and can hide content from crawlers. The short version: never lazy-load the hero image, and be careful about content that only appears after a scroll.

What Lazy-Loading Actually Does

Without lazy-loading, a browser starts fetching every image in the HTML as it parses the page. On a category page with forty product photos, that is a lot of work before anyone has scrolled. Lazy-loading tells the browser to wait until an image is close to the visible area, then fetch it.

Modern browsers can do this natively with a loading attribute on the image. That is usually the best option. JavaScript libraries that watch the scroll position can still be found on older sites. They work, but they add script, they can break if the library fails, and they sometimes swap a real image for a placeholder in a way that crawlers do not love.

The same idea is now applied to iframes, and sometimes to whole sections of HTML that are fetched only when they approach the viewport. That last pattern is where SEO problems usually start.

Why the Hero Image Should Never Be Lazy-Loaded

Largest Contentful Paint, the speed measure closest to "when did the main thing appear", is often the hero image, the main product photo, or a large heading banner. If that image is marked as lazy, the browser may treat it as something it can put off, even though it is the first thing the visitor should see.

In practice this looks like a blank or soft area at the top of the page, then a late pop-in of the main image. The rest of the page may be lighter, and a total-bytes report may look better, but the visit feels slower. Search systems that use field data will see that delay too.

A simple rule for developers:

  • The logo, the hero, the main product image above the fold, and any image that is likely to be the Largest Contentful Paint element should load normally, and should be easy for the browser to find early.
  • Images that sit clearly below the first screen can be lazy-loaded.
  • If you are not sure whether an image is in the first screen, assume it is, especially on mobile, where "the fold" is shorter than it looks on your monitor.

You should also give the hero a width and height, or an aspect-ratio, and consider preloading it if it is the LCP image. Lazy-loading and preloading the same image is a contradiction. Pick the eager path for that one file.

A quick check in a page speed test will usually name the LCP element. If that element is an image with a lazy attribute, remove it and test again. This is one of the highest-value, lowest-effort speed fixes on e-commerce and marketing templates.

When Lazy-Loading Helps

There are plenty of good uses. A long article with images between paragraphs, a collection grid, a footer of payment or trust badges, and a related-products row at the bottom of a product page are all sensible candidates. Lazy-loading those files reduces the work the browser has to do in the first second, which helps people on slower connections.

Native lazy-loading is enough for most of those cases. Keep the markup as a normal image with a real src, a useful alt attribute, and a loading value of lazy. Avoid replacing the image with a tiny placeholder that is later swapped by a script, unless you know the final image is still present in a crawlable form.

On large catalogues, this can be the difference between a usable category page and one that tries to pull down every product photo at once. It complements image compression and correct sizing. It does not replace them. A lazy-loaded 4,000-pixel photograph is still a heavy file when it finally loads.

When It Starts to Hurt SEO

Search systems can render pages, but they do not always scroll and wait in the same way a person does. Problems appear when lazy-loading is applied to more than decorative images.

Content, not just images, loaded on scroll

If product listings, article body text, reviews or internal links are injected only after a scroll event or an intersection observer, some crawlers may never see them. Infinite scroll and "load more" patterns have the same risk when they do not expose a real, paginated URL. The page a person can eventually reach is not always the page that was rendered on first load.

If a section matters for ranking, it should be in the HTML on first render, or at least in the rendered output without a user gesture. Lazy-load the images in that section if you need to, not the section itself.

JavaScript-only lazy-loading that fails closed

If the image src is empty, or pointed at a 1-pixel placeholder, until a script runs, then a failed script, a blocked file, or a crawler that does not execute that script will not see the image. Native lazy-loading keeps a real src in the HTML, which is much safer.

Lazy-loading images that carry meaning

Product photos, infographics, and images with important text should still have a real file and useful alt text in the markup. Lazy-loading can delay the download, but it should not remove the image from the document until a script decides it is needed.

These issues sit in the same family as other rendering questions, which is why they often come up in a technical SEO review. If you want a second opinion on whether Google is seeing the below-the-fold content, a site audit that includes rendered HTML is the right check, not just a lab speed score.

A Practical Implementation Checklist

When you next touch a template, run through this short list:

  1. Identify the likely LCP image on mobile and desktop. Do not lazy-load it. Consider preloading it.
  2. Use native lazy-loading on images that are clearly below the first screen.
  3. Keep real src and alt attributes in the HTML.
  4. Set width and height so the layout does not shift when images arrive.
  5. Do not lazy-load whole blocks of text, product grids, or navigation.
  6. If you use "load more" or infinite scroll, provide paginated, crawlable URLs as well.
  7. Test with JavaScript disabled and with URL Inspection in Search Console, not only with a speed tool.

This is also a theme and app problem on stores. A speed app or a theme setting that applies lazy-loading to every image is a common reason heroes suddenly start loading late. Turn the global setting off, then add lazy-loading only where it belongs. For a wider look at how we handle this kind of template work, see our comparison of technical SEO approaches with Builtvisible.

FAQs

Does lazy-loading stop Google from indexing images?

Native lazy-loading on a normal image tag usually does not, because the image URL is already in the HTML. Risk appears when a script is required to insert the real src, or when a whole section of content is fetched only after a scroll.

Should I lazy-load videos and iframes too?

Below-the-fold embeds are good candidates, because they can be very heavy. Do not lazy-load a video that is the main content of the page and sits at the top. As with images, the first visible media should be allowed to load promptly.

Is a JavaScript lazy-load library better than the native attribute?

Usually not, not any more. Native lazy-loading is simpler, has less to fail, and keeps a real image URL in the markup. A library is only worth considering if you need behaviour the browser cannot provide, and then it should still keep real URLs in the HTML.

How do I know if my hero is being lazy-loaded?

Inspect the hero image in the browser and look for a lazy loading attribute, or for a placeholder src that changes after load. A speed report that flags the LCP image as delayed is another clue. View the page source as well, in case a script is injecting the real image late.

Need a Hand Finding the Images That Are Slowing You Down?

If your lab scores improved after a lazy-load plugin, but the page still feels late to arrive, the hero is the first place I look. I can check which images should load immediately, which can wait, and whether any content is hidden behind a scroll. Start with a free SEO audit and we will go through the main templates together.

  • lazy loading
  • page speed
  • lcp
  • core web vitals
  • technical seo

Have a question about this for your own site?

A 15-minute call is usually enough to tell whether it applies to you and what to do first.

Book a 15-min callGet My Free SEO Audit

Related posts

Core Web Vitals Explained for Business Owners (WhiteLinko blog banner)

Technical SEO

Core Web Vitals Explained for Business Owners

LCP, INP and CLS explained in plain English for business owners: what each Core Web Vital measures, why it matters for sales, and how to read a report.

All blog posts →

Talk to WhiteLinko

Want this applied to your site?

Book a 15-minute call to talk through your goals, or start with a free SEO audit: a prioritised list of fixes, reviewed by a specialist.

Free PDF · 2026 edition

The WhiteLinko SEO Checklist

Six pages of tick boxes: technical, on-page, content, local, links, AI search and GA4.

Get the checklist
Free SEO Audit