Definition
Lazy loading is a technique that delays loading images, videos and iframes until they're about to become visible on screen: the browser only downloads what the visitor sees on arrival, and loads the rest as they scroll. Applied in the right place, it lightens a page's initial load time. Applied to the header image or video, usually the single largest element on the page, it does the opposite: the browser needlessly waits before loading what the visitor sees first, which hurts LCP.
How it works
Most CMSs and modern browsers turn on lazy loading by default for every image on a page, header included. That default setting is exactly the problem: a hero image, shown the moment the page opens, should instead load with priority. The rule is simple: images and videos above the fold, what a visitor sees without scrolling, should never be lazy loaded; anything further down the page can safely be.
Why it matters for your site
A site that ticks the lazy-loading box across the whole page gains in overall lightness, but loses on the metric that matters most for perceived speed, how fast the first visible content appears. It's a setting a marketing team degrades on its own without realizing it, by swapping a header image or adding a background video without checking whether the CMS's default setting lazy-loaded it.
The We-R perspective
We check this setting after every redesign, not just at launch: a theme, block or template change can silently re-enable default lazy loading on a header image that used to be excluded from it. It's a five-minute check that prevents a recently rebuilt page from losing an LCP improvement already earned.
Learn more
See also: LCP, Core Web Vitals, CMS. And to put it into practice: Les 7 erreurs SEO à éviter pour booster votre visibilité en ligne or how We-R builds and optimizes its clients' Webflow sites.
Sources: We-R, Webflow optimization method. Last updated: November 2026.
Have questions?
Transparency for informed decision-making.
Yes. The image or video visible the moment the page opens should load with priority, never lazy loaded, or it will hurt LCP.
On most CMSs, yes, often for every image including the header one: that default setting is exactly what needs checking and fixing.
Lazy loading delays loading a file until it's about to be visible. A CDN moves that file geographically closer to the visitor, without delaying its loading.
Not on its own, unless it delays the element measured by LCP: that specific case is what hurts SEO, not the technique in general.