Image lazy loading controls when images are downloaded, while decoding settings affect how images are decoded and displayed alongside other content. Lazy loading can defer downloads of offscreen images, reducing bandwidth use and processing work during the initial load. Decoding settings such as decoding=”async” may allow other content to appear sooner, though the effect may not be noticeable. The two serve different purposes, and the same settings are not appropriate for every image.
Lazy loading: deferring downloads of images that are not yet in view
According to web.dev, loading=”lazy” tells the browser to wait until an image enters or approaches the viewport before downloading it. The aim is not to wait until users see an empty space, but to defer images that are not currently needed so the browser can prioritize critical resources within the viewport.
- For example, thumbnails farther down a product listing that are not yet near the viewport are worth considering for lazy loading.
- Images and iframes that are not needed in the initial view can be loaded later, when they are more likely to be seen, reducing bandwidth use and processing work during the initial load.
Google’s developer documentation also recommends loading images shortly before users see them, but stresses that the implementation must be search-friendly. Along with improving performance, consider whether search services can process this content correctly.
Decoding settings: affecting how content appears, not deferring downloads
Unlike loading, decoding does not determine whether a download waits until an image is near the viewport. The three decoding settings listed by web.dev differ in how images are displayed alongside other content.
- async: Tells the browser it can decode the image asynchronously, potentially allowing other content to appear sooner.
- sync: Tells the browser that the image should be displayed at the same time as other content.
- auto: The default value, which lets the browser choose an appropriate approach.
When inserting an image into the DOM through JavaScript, you can also use the decode method of HTMLImageElement. However, the effects of the decoding attribute and decode method may only be readily noticeable with very large, high-resolution images, because these take longer to decode. Setting async therefore does not guarantee a noticeable speed improvement for every image.
Do not defer critical above-the-fold images along with images farther down the page
Lazy loading is for images that are not needed yet, rather than all images. In the Nuvemshop case reported by Search Engine Journal in 2026, an investigation identified several factors that together contributed to LCP issues: lazy-loaded above-the-fold images, a lack of priority signals for critical images, and transitions affecting element detection. The review also covered category and product pages.
When reviewing image settings, first distinguish between main images that need to be visible as soon as the page opens and images needed only after scrolling down. This case illustrates the importance of checking how above-the-fold content is loaded, but it does not mean that disabling lazy loading alone can solve performance problems on every page.
Image lazy loading and decoding: perspectives from across the web
Can lazy loading affect First Contentful Paint?
It can, especially when images visible as soon as the page opens are also lazy-loaded. Welly SEO warns that this setup may negatively affect First Contentful Paint (FCP). When choosing what to lazy-load, consider whether an image needs to appear in the initial view, rather than simply whether it is an image. This is a warning about a potential risk, not a claim that every page will be affected to the same extent.
Does lazy-loading images guarantee better search rankings?
No. Semrush suggests that lazy-loading images may shorten load times and improve PageSpeed Insights performance scores, so it can be a way to improve SEO. But better performance does not guarantee higher search rankings. The actual effect still depends on which images are lazy-loaded and how the page performed before the change.
What should you consider when implementing lazy loading for search services?
Along with improving speed, make sure search services can correctly process lazy-loaded content. Google's developer documentation recommends a search-friendly implementation, while another article advises against lazy-loading above-the-fold content so crawlers can access it immediately. These sources do not provide complete implementation steps, so their summaries alone cannot confirm that a particular implementation will allow the content to be indexed.
References
- 瞭解 JavaScript 搜尋引擎最佳化 (SEO) 基礎知識 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: What should you consider when implementing lazy loading for search services?
- Image performanceweb.dev — Discusses: Does lazy-loading images guarantee better search rankings?
- Learn Performanceweb.dev — Source used in the article above.
- Google’s Mueller Flags A Case On Why LCP Fixes Miss the Targetwww.searchenginejournal.com · 2026-07-02T22:50:47+00:00 — Source used in the article above.
- Definitive Javascript SEO Guideneilpatel.com · 2023-09-14T19:00:00+00:00 — Discusses: What should you consider when implementing lazy loading for search services?
- 圖片也可以提升網站曝光?圖片 SEO 必學 8 技巧!welly.tw · 2024-08-09T07:43:16.259Z — Discusses: Can lazy loading affect First Contentful Paint?
- HTML Image Tag: What It Is & How to Use It Properly in 2025www.semrush.com · 2021-05-25T12:03:00Z — Discusses: Does lazy-loading images guarantee better search rankings?
