What is lazy loading?
The term covers several implementations, including native browser behavior and custom scripts. It is not a single switch for all media. An image, iframe, video player and dynamically fetched article section can have different loading mechanisms and testing needs.
Native image loading is a browser decision
For img elements, MDN documents eager as the default loading value and lazy as deferred loading at a browser-defined distance from the viewport. A native lazy image does not require a custom scroll listener, and the exact fetch point should not be treated as fixed. Image loading attributes.
Start with resources outside the initial view
Google advises against lazy-loading content likely to be visible immediately when a page opens. Choose candidates after inspecting the page on the viewports you support rather than assuming that every template’s first image has the same role. Lazy-loading guidance.
Keep performance and content access separate
Google recommends loading relevant deferred content when it becomes visible, without requiring clicks or other user actions. Test the rendered HTML to see whether the intended content and media URLs are present. That check establishes accessibility to the renderer, not guaranteed indexing or better rankings. Testing lazy-loaded content.
Lazy and eager image examples
These are illustrative images with sample paths and dimensions. Replace them with your real assets and their intrinsic dimensions; the samples are escaped code, not requests for those files.
<img src="/gallery-example.webp"
alt="Example gallery subject"
width="800" height="600" loading="lazy"><img src="/initial-example.webp"
alt="Example initial subject"
width="800" height="600" loading="eager">Reserve space and identify the LCP resource
MDN explains that width and height let the browser determine an image’s aspect ratio before it loads and reserve space for it. Use correct dimensions rather than copying sample values. Image dimensions.
web.dev advises never lazy-loading the LCP image because it introduces unnecessary resource-load delay. Identify the actual LCP element in a measurement; do not assume every hero is the LCP image. LCP resource loading.
Do not promise a fixed speed gain
A page with few deferred resources may behave differently from a long gallery. Check actual resource requests and whether the initial content appears promptly. Do not report a percentage reduction, a millisecond gain or a ranking improvement without measurements that support it.
Check what the theme already does
Inspect the markup and rendered page before adding another loading library. On a gallery or service page, verify that deferred images appear when needed, that useful alt text remains available and that the initial content is not delayed. Test at mobile and desktop sizes.
Lazy-loading questions
Will loading="lazy" wait until the image is on screen?
Not necessarily. MDN defines a calculated distance from the viewport chosen by the browser. An image can be fetched before it is visible, so use network observations to understand the behavior rather than treating the attribute as an exact scroll threshold.
Does a passing rendered-content test guarantee indexing?
No. Google’s guidance uses rendered HTML to check whether deferred content loaded. Loading the content correctly addresses that implementation issue; it does not establish that the page will be indexed or that its rankings will improve.
Related terms
Largest Contentful Paint · Cumulative Layout Shift · Mobile-first indexing
Sources
Explore this topic: Lazy Loading and SEO: Core Web Vitals and Crawlability.