Lazy loading defers fetching resources — usually images and iframes — until the user scrolls close enough to need them. It reduces initial page weight substantially.
Modern browsers support it natively through the loading="lazy" attribute, which requires no JavaScript. The browser decides when to fetch based on scroll position and connection speed. Before native support this required intersection observers or libraries, many of which are still in use and now unnecessary.
On image-heavy pages lazy loading can cut initial payload dramatically, improving load metrics and reducing bandwidth on mobile connections. The common and costly mistake is lazy loading the hero image, which directly delays Largest Contentful Paint and makes the page measurably slower in exactly the metric that matters.
Apply loading="lazy" to images below the fold and loading="eager" to the hero. Always set width and height so space is reserved and layout does not shift as images arrive. If a JavaScript lazy loading library is still in place, consider removing it in favour of the native attribute.
Want to learn more? Explore our SEO Glossary or check out our expert guides on SEO strategies.