Your product photos help shoppers decide whether to buy, but they can also make a product page feel slow. The problem is often not the number of images alone. It is which image the browser loads first: a gallery thumbnail or an offscreen recommendation can compete with the main product photo your visitor is waiting to see.
A practical ecommerce image-loading strategy gives the main, visible product photo priority and lazy-loads images that shoppers cannot yet see. Here is how to make that distinction, implement it across common store pages, and check that the changes actually work.
What is the LCP product image?
Largest Contentful Paint (LCP) measures when the largest eligible piece of content in the visible part of a page finishes rendering. On many product pages, that element is the main product photo. On a category page, it might instead be a banner, a product card image, or a text block. Do not assume the same image is the LCP element on every template or screen size.
This matters because a browser may discover several images at once: the main photo, gallery thumbnails, recommended products, badges, and promotional graphics. If your most important visible image waits behind less important downloads, the page can appear incomplete even while other assets are loading.
Start by identifying the actual LCP element on representative product and collection pages. PageSpeed Insights can show field and lab performance where data is available; Chrome DevTools can help you inspect what loads, when it loads, and which element a test identifies as LCP. Test on a mobile-sized viewport as well as desktop, since the visible layout may differ.
Prioritize the main product photo without loading everything at once
Keep the above-the-fold image eager
If the main product photo is visible as soon as the page opens, do not lazy-load it. Lazy loading delays an image until it is near the viewport, which can postpone the very photo the shopper came to see. Check your theme, image app, and gallery component: automatic lazy-loading rules sometimes catch the first gallery image by mistake.
If your storefront controls the image markup, the visible main photo can use loading=”eager” or omit the loading attribute. You can also consider fetchpriority=”high” for that image. Fetch priority is a hint, not a guarantee, and it works best when reserved for a small number of genuinely important resources. Marking every product image as high priority defeats the purpose.
Help the browser discover the correct image early
Even an eager image may start late if it is inserted only after JavaScript runs, hidden behind a gallery initialization step, or referenced in a way the browser cannot find promptly. Where your theme allows it, render the initial product image in the page’s image markup rather than waiting for an interaction or script to create it.
A preload can help when a critical image would otherwise be discovered late, but use it selectively. Preloading the wrong variant may waste bandwidth, especially when mobile and desktop layouts use different images. If you preload a responsive image, make sure the preload matches the image source the browser is expected to select. Test before keeping the change.
Serve an appropriately sized file
Priority cannot rescue an unnecessarily large image. Deliver a version sized for its display area, while allowing enough resolution for sharpness on higher-density screens. Responsive image options such as srcset and sizes let the browser choose from available widths. Modern formats can reduce file size, but compare visual quality on details shoppers care about, such as texture, color, and packaging text.
Check your platform’s image settings before adding another optimization app. Your theme or ecommerce platform may already generate multiple sizes and formats. The goal is to avoid sending a full-resolution zoom image as the first image on a small mobile screen—not to make product photography look worse.
Lazy-load images below the fold
Lazy loading is most useful for images that are not needed for the initial view. On a product page, these may include later gallery images, customer photos, related products, and content farther down the page. On a collection page, product cards well below the first visible row are common candidates.
For eligible images, native loading=”lazy” is often a sensible starting point. Browsers typically begin fetching lazy images before they actually enter the viewport, so they can be ready as a visitor scrolls. Exact timing varies by browser and conditions, which is why you should test the experience rather than assuming every image will appear instantly.
Be more careful with images near the top of the page. The first row of collection products may be visible immediately on a desktop screen or just below a mobile header. A blanket “lazy-load all product cards” rule can delay those images. Likewise, a gallery image that becomes visible immediately after a shopper taps a thumbnail should not leave them staring at an empty frame. Test gallery interactions and consider how quickly the next image needs to be available.
A page-by-page loading plan for your store
| Page area | Likely approach | What to check |
|---|---|---|
| Main product photo visible on arrival | Load eagerly; consider high fetch priority | Is it actually the LCP element on mobile and desktop? |
| Additional gallery photos | Defer when not initially visible | Do thumbnail taps and swipes still feel responsive? |
| First visible collection products | Avoid indiscriminate lazy loading | Which cards appear above the fold at common screen sizes? |
| Products farther down a collection page | Lazy-load | Do images appear in time during normal scrolling? |
| Related products and lower-page content | Usually lazy-load | Are they truly outside the initial viewport? |
These are starting points, not universal rules. A promotional banner may be the LCP element on one collection template, while a product image is the LCP element on another. Prioritize what the visitor actually sees first.
How to implement and test changes without guessing
- Choose representative pages. Include a popular product page, a product with many gallery photos, and a collection page with plenty of cards. Check mobile and desktop layouts.
- Record a baseline. Note the identified LCP element, image requests, file sizes, and whether visible photos appear promptly. Where available, compare field data with lab tests rather than relying on one test run.
- Fix the first visible image. Remove lazy loading from the main photo if it is present. Make sure the initial image is discoverable early and served at a suitable size. Consider a high-priority hint only for a genuinely critical image.
- Defer offscreen images. Apply lazy loading to lower-page imagery, then verify that gallery interactions and scrolling remain smooth.
- Retest and compare. Look for changes in LCP, image request order, and what a shopper sees as the page opens. Test on a slower mobile connection as well as your usual connection.
Make one group of changes at a time. If you change your theme, image format, gallery app, and lazy-loading settings together, it becomes difficult to tell what helped—or what caused a new problem. If an app and your theme both manage image loading, check for overlapping rules before adding another tool.
Common image-loading mistakes to avoid
- Lazy-loading every image: This can delay the main product photo and the first visible collection cards.
- Giving every image high priority: Priority hints are useful because they distinguish critical resources from the rest.
- Preloading multiple gallery photos: Downloading images a shopper may never view can compete with the initial page content.
- Optimizing only file size: Compression helps, but an image discovered late can still appear late.
- Testing only the homepage: Product and collection templates often have different image behavior—and different commercial importance.
Your next step does not need to be a store-wide rebuild. Audit one high-traffic product template first: find the visible main photo, confirm it is not lazy-loaded, check that its file is appropriately sized, and defer photos farther down the page. Once that works, apply the same decision process to your collection pages.
Frequently Asked Questions
Should I lazy-load the main product image?
Usually not if it is visible when the page opens. Load that image eagerly, then test whether it is the LCP element. Other gallery images that are initially offscreen may be suitable for lazy loading.
Will lazy loading hurt product image SEO?
Lazy loading is not inherently a problem, but important images should remain accessible in the page and load reliably. Avoid implementations that require unusual user actions before search engines or shoppers can reach an image. Test rendered pages if a theme or app inserts images with JavaScript.
Should I use both image preloading and fetch priority?
Not by default. Fetch priority can signal that an already discoverable image matters; preloading can help the browser find an image earlier. Use either only when it solves an observed problem, and check that you are not causing an unnecessary download or prioritizing the wrong responsive variant.
What if my ecommerce platform controls image loading?
First review your theme settings and any image or speed apps. Many platforms handle responsive image sizes automatically, while themes determine which images are lazy-loaded. If you cannot change the markup yourself, give your developer or theme support team the specific page, image, and test result you want them to investigate.