✦ Free SEO tool

Lazy Loading Images Checker

See which images on a page are lazy-loaded, which ones further down should be, and whether the first image is being delayed by mistake.

Fetching and analysing the page…

5 of 5 free checks left today. Create a free account for unlimited checks.

Lazy Loading Images Checker - results and guide

What the Lazy Loading Images Checker checks

  • Images using the native loading="lazy" attribute
  • Images lazy-loaded by JavaScript through data-src
  • Images below the first screen that still load immediately
  • A first image that is lazy-loaded, which delays Largest Contentful Paint
  • fetchpriority="high" on the main image
  • Lazy images without width and height, which cause layout shift
  • Iframes such as video embeds and maps

What is lazy loading?

Lazy loading means an image is downloaded only when the visitor scrolls close to it. Add loading="lazy" to an <img> or <iframe> and the browser handles the rest, with no script. Images a visitor never scrolls to are never downloaded, which saves data and leaves the connection free for what is on screen first.

Before browsers supported this natively, sites used JavaScript libraries that kept the real address in a data-src attribute. Those still work but depend on a script running, and crawlers that do not execute it may never see the image.

What should not be lazy-loaded

The image at the top of the page. Lazy loading tells the browser to wait, and if that image is the largest thing on screen, waiting delays Largest Contentful Paint. This is one of the most common causes of a poor LCP, and it usually happens when a plugin adds loading="lazy" to every image without exception.

The hero image should load normally and can be marked fetchpriority="high". Everything below the first screen should be lazy. Every lazy image also needs width and height, so the browser reserves its space and the page does not jump when it arrives. Measure the effect with the Core Web Vitals Checker.

How to use the Lazy Loading Images Checker

  1. Enter the address of the page you want to check. You can leave out https://.
  2. Press Check images. The page is fetched from our servers, the way a search engine crawler would fetch it.
  3. Read the findings from top to bottom: problems first, then warnings. Each one says what to change.

Common problems and how to fix them

The first image is lazy

Remove loading="lazy" from it, or tell your image plugin to skip the first image. Add fetchpriority="high".

Images further down load immediately

Add loading="lazy" to them. In WordPress this is automatic for images inserted through the editor; check images hard-coded in templates.

Images depend on a JavaScript lazy loader

Switch to the native attribute with a real src. It is supported by every current browser and needs no library.

Frequently asked questions

Does lazy loading help SEO?
Yes, when used correctly. It speeds up the initial load, which helps Core Web Vitals. Used on the main image it does the opposite.
Can Google index lazy-loaded images?
Yes, with the native loading attribute, because the image address is in the src. JavaScript lazy loading that hides the address is riskier.
Should I lazy-load every image?
No. Leave the logo and the main image at the top of the page to load normally.
How does this tool decide what is below the first screen?
It uses position in the HTML. The first image is treated as visible at once, and images from the fourth onward as further down. Check the real layout where that does not hold.
Monitor Today. Stay Ahead.

SEO gets visitors to your site. Uptime keeps them there.

Monitor 5 websites free forever and get alerted the moment one goes down. No credit card required.