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

Lazy loading images: faster pages without hurting SEO

Updated · 7 min read

Short answer Lazy-load the images below the first screen and load the top photo normally. Google warns never to lazy-load the main image, because it slows the page's key speed number. Use the browser's built-in loading="lazy" so Google still finds every image without scrolling. Most site builders already do this, and many include a CDN too.

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

Book a call

Which images to lazy-load, and which never to

Lazy loading means the browser waits to download an image until the visitor scrolls near it. It saves data on photos people may never reach. The catch is the top of the page: an image that is already on screen should load right away.

ImageLazy-load?
The big photo or banner at the top (hero image)No. Load it normally
Your logo and anything else on the first screenNo
Project galleries, team photos, reviews lower downYes
Embedded Google Map or YouTube video lower downYes
Images inside a slider that only appear after a tapYes, but keep them in the page code (see below)

Google's web.dev team states the rule plainly:

"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 for the web)

LCP (Largest Contentful Paint) is how long the biggest image or text block on the first screen takes to appear. It is one of the three Core Web Vitals Google uses; what they are and how much they affect ranking. On most service business pages, the LCP element is the hero photo. web.dev's guide to LCP adds that lazy-loading it "will always lead to unnecessary resource load delay" (web.dev: Optimize Largest Contentful Paint).

Does lazy loading hurt SEO?

Not if it's done the standard way. Lazy loading hurts only when Google can't find the image at all. Google's page on lazy-loaded content explains why:

"Google Search does not interact with your page." (Google Search Central: Fix lazy-loaded content)

So an image that appears only after a scroll, a click or a swipe may never be seen by Google. Google recommends methods that load images when they come near the screen without needing a user action: the browser's built-in lazy loading, or a script built on the IntersectionObserver API (same page).

Two more rules from Google decide whether an image can show in search:

  • Google finds images in the `src` attribute of an image (`img`) tag, and it "doesn't index CSS images" (Google Search Central: Google image SEO best practices). A photo set as a background in the design code won't appear in Google Images.
  • Some older lazy-load scripts hide the real file in a field like `data-src` and swap it in later. Google says to check that image URLs end up in the `src` attribute of the rendered page (Google Search Central: Fix lazy-loaded content).

How to add lazy loading

On a custom-coded site, it's one setting in the image tag, loading="lazy":

`img src="deck-repair.jpg" alt="Rebuilt cedar deck" width="1200" height="800" loading="lazy"`

  • loading="lazy" works in all major browsers, and web.dev recommends it "for most use cases" (web.dev: Browser-level image lazy loading for the web).
  • width and height let the browser save the right space before the image arrives, so the page doesn't jump. web.dev recommends them on every image (same page).
  • iframes (embedded maps, videos, booking widgets) take the same `loading="lazy"`. web.dev says lazy-loading offscreen iframes saves data and can leave more bandwidth for the main image (web.dev: It's time to lazy-load offscreen iframes).

Chrome doesn't wait until the image is on screen. It starts loading when the image is 1,250 pixels away on a fast connection and 2,500 pixels away on a slow one, so visitors rarely see a blank space (web.dev: Browser-level image lazy loading for the web).

On a site builder, check before you add anything:

PlatformWhat it already does
WordPressAdds lazy loading automatically. Since version 6.3 it leaves the first three images alone (the threshold "has been modified from 1 to 3") and marks the likely main image as high priority (Make WordPress Core, 2023)
WixShows small placeholder images first, then swaps in full-quality versions; also compresses uploads under 25 MB (Wix Help Center)
SquarespaceCreates "multiple copies of the image with different sizes" and loads the right one for the screen (Squarespace Developers: ImageLoader)

On WordPress, a speed plugin or theme can override these defaults. If the hero photo still lazy-loads, the plugin's setting to exclude the first images is the fix.

Too much lazy loading makes a page slower

Lazy-loading everything is the most common mistake. In a lab test on a sample WordPress site, turning off lazy loading made archive pages' LCP 13% to 15% faster, because the top images had been lazy-loaded. Lazy-loading only the images below the first screen removed the slowdown and kept the data savings (web.dev: The performance effects of too much lazy loading).

Keep the gain in proportion. When Google's Lighthouse tool dropped its "offscreen images" check in version 13, it gave the reason that "Offscreen images are already deprioritized by the browser" (Chrome for Developers: What's new in Lighthouse 13). Lazy loading lower images mostly saves visitors' data; fixing the top image is what makes the page feel fast.

Do you need a CDN for images?

A CDN (content delivery network) keeps copies of your images on servers in many cities and sends each visitor the nearest copy. web.dev calls a CDN the best way to get files close to your users, and says image CDNs often shrink files too (web.dev: Optimize Largest Contentful Paint).

Your setupCDN?
WixAlready built in. Wix says its CDN delivers content "from the server geographically closest to them" (Wix Help Center)
Other hosted buildersCheck the platform's help pages; most handle hosting and delivery for you
WordPress or a custom site on your own hostingWorth adding. Cloudflare's caching is "Available on all plans," including the free one (Cloudflare Docs: Cache)

A local business serves people in one area, so a CDN matters less than for a national brand if your host's servers are nearby. It still helps when the host is far away or slow. Two cautions from web.dev: serving images from a different domain than the page adds a connection delay, and links with unique tracking codes can stop the CDN from using its saved copies (web.dev: Optimize Largest Contentful Paint).

Responsive images: the third speed fix

Responsive images give the browser several sizes of one photo, so a phone downloads a small file instead of a desktop-sized one. Google notes that pages do this with `srcset` or the `picture` element (Google Search Central: Google image SEO best practices). Squarespace creates the sizes for you. On a custom site, ask your developer whether your images use `srcset`.

How to check your site

  1. Run your home page and main service page through PageSpeed Insights on mobile. Its "LCP request discovery" check flags a main image that is lazy-loaded and tells you to "Avoid loading=lazy for the image" (Chrome for Developers: LCP request discovery).
  2. In Search Console, run URL Inspection on the same page and view the rendered page. Google says to confirm your image URLs appear in the `src` of the image tags (Google Search Central: Fix lazy-loaded content).
  3. Open the page on your phone over mobile data and scroll fast. Images should be there by the time you reach them.

More on these reports: Google Search Console for a small business.

Example

Illustrative cases, not measured results.

A roofer whose theme lazy-loads everything

PageSpeed flags the hero photo of a finished roof. The owner sets the speed plugin to skip the first image. The rest of the 40-photo gallery stays lazy-loaded.

A dental office with a map at the bottom

The embedded Google Map loads on every visit, even for patients who never scroll down. Adding `loading="lazy"` to the map's iframe stops it from competing with the top of the page.

A landscaper on cheap shared hosting

The WordPress site's images load slowly from a far-off server. The owner adds Cloudflare's free plan and resizes 5 MB phone photos before uploading. Both help; the resizing helps more.

FAQ

Should I lazy-load my logo?

No. The logo sits on the first screen, so it should load right away. Lazy loading is for images people reach by scrolling.

Will Google Images still show my lazy-loaded photos?

Yes, if you use the browser's built-in lazy loading and the image is a normal image (`img`) tag with the file in `src`. Images set as CSS backgrounds won't show, lazy or not.

Is a lazy-loading plugin or library still needed?

Usually not. The built-in `loading="lazy"` attribute works in all major browsers. A script is worth it only for special cases, like a custom gallery.

Does a CDN improve rankings?

Not directly. It can make images arrive faster, which helps your speed numbers and your visitors. Google says it still shows the most relevant page even when the page experience is poor (Google Search Central: page experience).

Different for you?

Keep learning

NextLazy Loading and SEO: Faster Pages Without Hiding ContentHow to lazy load images and embeds so pages load faster and Google still sees them: the built-in browser setting, what never to lazy load, and how to check.

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: Google image SEO best practices
  3. Google Search Central: Understanding page experience in Google Search results
  4. web.dev: Browser-level image lazy loading for the web
  5. web.dev: The performance effects of too much lazy loading
  6. web.dev: Optimize Largest Contentful Paint
  7. web.dev: It's time to lazy-load offscreen iframes
  8. Chrome for Developers: LCP request discovery
  9. Chrome for Developers: What's new in Lighthouse 13
  10. Make WordPress Core: Image performance enhancements in WordPress 6.3
  11. Wix Help Center: Site performance: how Wix improves your site's loading time
  12. Squarespace Developers: ImageLoader
  13. Cloudflare Docs: Cache