PERFORMANCE · SEO GLOSSARY
Lazy Loading SEO
The SEO implications of lazy loading — deferring loading of images and other resources until they enter the viewport — which improves initial page load performance but can harm LCP if the main content image is lazy-loaded, and can prevent off-screen content from being indexed if text content is lazy-loaded.
Definition
Lazy loading in an SEO context refers to the performance optimisation of deferring the loading of non-critical resources (images, iframes, below-the-fold content) until the user scrolls them into view — and the specific SEO risks created when this optimisation is applied incorrectly. Lazy loading is universally positive for SEO when applied to off-screen, non-critical resources. It becomes an SEO problem in two specific scenarios: (1) **Lazy-loading the LCP image**: the LCP element (Largest Contentful Paint — the largest visible content element) must load as quickly as possible. If the hero image (which is usually the LCP) has `loading="lazy"`, the browser defers its loading until the viewport calculation is complete — adding significant delay to the LCP metric. Correct practice: the hero image should be `loading="eager"` (or simply omit the loading attribute, which defaults to eager) and have a `<link rel="preload">` in the `<head>` for maximum performance. (2) **Lazy-loading text content**: if text content (headlines, body copy, link text) is hidden in off-screen elements that are loaded lazily or conditionally, Googlebot may not be able to access that content. Googlebot renders the initial viewport and executes JavaScript, but content that requires user scroll interaction to trigger loading may not be fully accessible to the crawler. Correct implementation: use `loading="lazy"` only on images below the fold; never defer text content loading; use `loading="lazy"` on images in lists/grids that appear below the initial viewport. HTML lazy loading attribute: the `loading="lazy"` HTML attribute for images is the modern browser-native lazy loading mechanism. IntersectionObserver-based JavaScript lazy loading (legacy approach) has the same SEO implications and is increasingly unnecessary since native lazy loading works in all modern browsers.
Why it matters for SEO
Lazy loading is one of the most commonly misapplied performance optimisations. Many sites apply `loading="lazy"` globally to all images (a common performance tutorial recommendation) without recognising that this damages LCP for hero images. The result is worse Core Web Vitals scores from an optimisation intended to improve performance. Understanding where lazy loading helps (below-fold images) versus where it hurts (LCP element, text content) is essential for correct implementation.
How DeepSEOAnalysis checks this
DeepSEOAnalysis checks for the LCP element on audited pages and validates whether it has incorrect `loading="lazy"` attribution. CrUX LCP field data at p75 reflects the real user impact of any lazy loading configuration — poor LCP scores with an identifiable hero image are often caused by incorrect lazy loading. The audit also checks for text content that may be conditionally loaded or hidden in ways that affect crawler access.
GLOSSARY
Related terms
performance
LCP Image
The image element identified by Chrome as the Largest Contentful Paint (LCP) candidate on a page — the largest visible image in the initial viewport that determines the LCP timing score, typically the hero image, product thumbnail, or featured photo at the top of the page.
Read definition →performance
Performance Budget
A predefined set of constraints on web page performance metrics — such as maximum JavaScript bundle size, maximum LCP time, or maximum total blocking time — used to prevent performance regression as a website evolves, by alerting or failing builds when the page\'s performance metrics would exceed the defined thresholds.
Read definition →performance
Render-Blocking Resources (SEO)
CSS stylesheets and JavaScript files that block the browser from rendering page content until they are downloaded and processed — a primary cause of poor LCP and FCP (First Contentful Paint) scores, requiring deferral, async loading, or inline critical CSS strategies to resolve.
Read definition →technical
JavaScript Indexing
The process by which Googlebot crawls and indexes content rendered by JavaScript — including the rendering pipeline (crawl, queue for rendering, execute JavaScript, index rendered content), timing delays between first crawl and rendering, and implications for structured data that must be in server-rendered HTML to be processed by the initial fetch.
Read definition →performance
WebP (SEO)
The WebP image format developed by Google — offering significantly smaller file sizes than JPEG and PNG at equivalent visual quality — which improves page loading performance (LCP in particular) and is supported by all modern browsers, making it the recommended image format for web images.
Read definition →See how your site scores on Lazy Loading SEO.
The free DeepSEOAnalysis audit checks lazy loading seo and 100+ other signals. Full report, no signup.
Run a free audit →