Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Lazy Loading and SEO: Faster Pages Without Hiding Content

Updated · 6 min read

Short answer Lazy loading is safe for SEO when you use the browser's built-in loading="lazy" on photos and embeds further down the page. Never lazy load the main image at the top: it slows the page's biggest element. Google doesn't scroll or click, so content must load once it's on screen. Check with Search Console's URL Inspection.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Is lazy loading good for SEO?

Yes, if it's done right. Lazy loading means the browser waits to download a photo or video until the visitor scrolls near it, so the first screen loads sooner. Google calls it "a common performance and UX best practice," then warns that done wrong, "this technique can inadvertently hide content from Google" (Google Search Central).

The rule that keeps it safe:

"Make sure that your lazy-loading implementation loads all relevant content whenever it is visible in the viewport." (Google Search Central, "Fix lazy-loaded content")

The viewport is the part of the page on screen. The reason, on the same page: "Google Search does not interact with your page." Google doesn't scroll, click or swipe. A photo that loads only after a click may never be seen.

Speed itself counts for little in ranking. Google uses page experience as a tiebreaker, not a lift for weak pages: see Core Web Vitals and Google ranking.

What to lazy load, and what never to

On the pageLazy load?Why
Main photo at the top (hero banner)NeverIt is usually the page's biggest element, so delaying it slows LCP
Logo and anything else on the first screenNoVisitors see the wait
Project photos, team photos, galleries further downYesSaves data until someone scrolls there
YouTube videos and Google Maps embeds below the first screenYesEmbeds are heavy; web.dev measured about 500 KB saved per YouTube embed
Photos set as CSS backgroundsCan'tThe setting works only on normal image tags
Text, reviews or prices that appear only after a clickAvoidGoogle doesn't click, so it may not see them

Sources: web.dev's image and iframe lazy-loading guides; Google Search Central.

LCP (Largest Contentful Paint) is Google's measure of how fast the main image or text appears. web.dev's warning:

"Don't lazy-load images that are likely to be in-viewport when the page loads, especially LCP images." (web.dev: Browser-level image lazy loading)

Google says the same for search: lazy loading on content "likely to be immediately visible" makes it "take longer to load" (Google Search Central).

Too much lazy loading is a real problem, not a theory. In a 2022 lab test of a default WordPress theme, turning off its lazy loading made the main image appear 13–15% faster on a page of posts, at the cost of loading about twice the image data up front (web.dev).

Background photos have a second catch: "Google doesn't index CSS images" (Google Search Central: Image SEO). If a photo should show in Google Images, use a normal image tag.

How to add lazy loading to images

Use the browser's built-in setting. Add `loading="lazy"` to each image or embed below the first screen, and give each image a `width` and `height`. Without sizes, the layout jumps as photos arrive, which hurts CLS, Google's layout-shift score (web.dev).

Every major browser supports it for images: Chrome and Edge, Firefox since version 75, Safari since 15.4. For embeds (iframes), Firefox added it in version 121 and Safari in 16.4 (web.dev).

The browser starts loading early, not at the last second. Chrome begins about 1,250 pixels before an image reaches the screen on a fast (4G) connection, and 2,500 pixels on 3G or slower. You can't change those distances (web.dev).

Do I need a lazy loading plugin or JavaScript library?

Usually not. web.dev:

"With full support of lazy loading built into modern browsers, you probably don't need a third-party library or script to lazy-load images." (web.dev)

Libraries still have uses: very old browsers, or exact control over timing (web.dev). If you keep one, it must load images on screen without a scroll, per Google's rule above.

WordPress, Wix and Squarespace

WordPress adds lazy loading on its own and skips the first images it expects on screen. WordPress 6.3 (2023) raised that default from 1 image to 3 and began skipping header images in classic themes (Make WordPress Core). A speed plugin set to lazy load every image can undo that, so check the top image after installing one.

Hosted builders decide for you. You can't edit the code, but you can test the result the same way. More on platforms: Wix, Squarespace or WordPress for SEO.

Should the main image load first?

Yes. Besides removing `loading="lazy"` from it, mark it important. Chrome's PageSpeed check for the main image passes when the image:

  • is in the page's HTML from the start (or preloaded), not added later by a script or CSS;
  • has `fetchpriority="high"`;
  • doesn't use `loading="lazy"`.

Source: Chrome for Developers, "LCP request discovery." WordPress 6.3 adds `fetchpriority="high"` for you and never puts it on a lazy-loaded image. Its developers report the attribute typically improves LCP by 5–10% (Make WordPress Core).

How to check that Google sees lazy-loaded images

  1. Open Search Console, paste the page address into URL Inspection, and run a live test.
  2. View the rendered HTML (the page as Google built it).
  3. Search it for your photo file names.

Google's pass test: if each image or video address appears in the `src` attribute of its image or video tag in the rendered HTML, your setup "works correctly" (Google Search Central).

If the file name sits in a `data-src` field but not in `src`, the script never ran for Google. Then run PageSpeed Insights on mobile and look for the main-image warning. New to Search Console: the reports a small business should read.

Infinite scroll and "load more" buttons

A blog or gallery that loads more as you scroll needs a separate address for each chunk, such as `?page=2`, with normal links between them, so Google can reach every part (Google Search Central). Without it, older posts may never be indexed: see crawled or discovered, currently not indexed.

Example

Illustrative cases, not measured results.

A landscaper's project gallery

Forty photos on one page, all downloading at once. She adds `loading="lazy"` to every photo except the first, with set sizes. The first screen now loads one photo instead of forty, and URL Inspection still shows all forty file names.

A dentist whose banner loads last

A speed plugin lazy loads every image, including the smile photo at the top. PageSpeed flags the main image. Excluding that one photo from the plugin and marking it high priority clears the warning.

A roofer's map and videos

The contact page embeds a Google Map and two YouTube videos near the bottom. Lazy loading the three embeds cuts what a phone downloads before the visitor scrolls, and the phone number at the top shows sooner.

FAQ

Does Googlebot see lazy-loaded images?

Yes, when they load once on screen, as the browser's built-in setting does. Google doesn't scroll or click, so images that wait for those actions can be missed.

Is lazy loading a ranking factor?

No. It can speed up a page, and Google uses page experience only as a tiebreaker between similar pages.

Can I lazy load text?

Avoid it. Text that loads only after a click or tap may be invisible to Google, and text is small, so there's little speed to gain.

What does "Largest Contentful Paint image was lazily loaded" mean?

Your main image waits for lazy loading, which delays the page. Remove `loading="lazy"` from that one image, or exclude it in your plugin.

Should I lazy load my logo?

No. It's on the first screen and small, so lazy loading only makes it appear later.

Different for you?

Keep learning

NextCore Web Vitals monitoring: track LCP, INP and CLS over timeHow to track Core Web Vitals month to month with Search Console, CrUX Vis and GA4, why fixes take 28 days to show, and what INP replacing FID changed.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Fix lazy-loaded content
  2. Google Search Central: Image SEO best practices
  3. web.dev: Browser-level image lazy loading for the web
  4. web.dev: It's time to lazy-load offscreen iframes
  5. web.dev: The performance effects of too much lazy loading
  6. Chrome for Developers: LCP request discovery
  7. Make WordPress Core: Image performance enhancements in WordPress 6.3