Blog › Site speed and Core Web Vitals › How Do You Improve LCP on Ecommerce Product Pages?
Noibu blog

How Do You Improve LCP on Ecommerce Product Pages?

How do you improve LCP on ecommerce product pages?

To improve LCP on ecommerce product pages, make the main product image load first, cut server response time, remove scripts that block rendering, and serve right-sized modern image formats. Then measure LCP from real shoppers, by template and device, because lab scores often miss what mobile shoppers experience.

Last updated November 16, 2026

Largest Contentful Paint (LCP) measures when the biggest piece of content in the viewport finishes rendering. On a product page that is usually the main product image, which is also the thing a shopper came to see. This playbook walks through why product page LCP runs slow and the changes that move it, in the order most teams should try them.

Key takeaways

  • A good LCP is 2.5 seconds or less at the 75th percentile of real page loads, per Google's web.dev guidance.
  • On most product pages the LCP element is the main product image, so it must be discovered and fetched first.
  • Server response, render-blocking scripts and late-loading images account for most slow product page LCP.
  • Measure with field data by page template and device; a fast Lighthouse score can hide a slow mobile LCP.

Part of: Noibu's Performance Agent

What counts as a good LCP on a product page?

Google's web.dev guidance on LCP sets the thresholds: 2.5 seconds or less is good, more than 4.0 seconds is poor, and anything between needs improvement. The score is taken at the 75th percentile of page loads and split by mobile and desktop, so three in four visits need to hit the target, not the average visit. Product pages are often the slowest template on a store because they carry the largest images and the most apps.

LCP matters on product pages because it is the moment a shopper sees the product. Until then, they are looking at a header, a spinner or an empty gallery frame. The connection between Core Web Vitals and revenue is covered in how Core Web Vitals affect ecommerce conversion.

Why is LCP slow on ecommerce product pages?

Google's guide to optimizing LCP breaks LCP into four parts: time to first byte from the server, the delay before the browser starts loading the LCP resource, the time it takes to download that resource, and the delay before it is rendered. Product pages tend to lose time in each part:

  • Server response: product pages pull variants, inventory, pricing and recommendations, and uncached responses can take a long time on busy days.
  • Late discovery: gallery images injected by JavaScript, set as CSS backgrounds or marked for lazy loading are found late by the browser.
  • Heavy images: full-resolution photography served to phones, in older formats, takes longer to download.
  • Render delay: render-blocking CSS and scripts, web fonts and A/B testing snippets that hide the page hold back the paint even after the image arrives.

The product page LCP playbook

  1. 1

    Find the LCP element

    Confirm in field data or browser tools which element is LCP on mobile and desktop for your product template.

  2. 2

    Load it first

    Put the main image in the HTML, never lazy-load it, and add fetchpriority="high" or a preload.

  3. 3

    Right-size the image

    Serve responsive sizes with srcset and modern formats such as WebP or AVIF from a CDN.

  4. 4

    Cut server time

    Cache product pages at the edge and move slow lookups like recommendations off the critical path.

  5. 5

    Unblock rendering

    Defer non-critical scripts, inline critical CSS, and remove page-hiding test snippets.

  6. 6

    Measure real shoppers

    Track LCP at the 75th percentile by template and device after each change.

How do you make the main product image load first?

The browser can only start fetching the LCP image once it knows the image exists. If the image URL sits in the HTML as a normal image tag, the browser finds it almost immediately. If it is built by a gallery script, hidden behind a carousel that initializes later, or set as a background in CSS, the browser finds it late. Render the first gallery image as a plain image in the server HTML, give it explicit width and height, and add fetchpriority="high" so the browser prioritizes it over other images.

Check for loading="lazy" on the first image. Many themes apply lazy loading to every gallery image by default, including the first. That tells the browser to wait until layout is known before fetching, which is exactly wrong for the LCP element. Keep lazy loading for the second image onward and for content below the fold.

How much does image size matter?

A large share of LCP on product pages is often download time for the image itself. Serve the image at the size it is displayed, using srcset and sizes so phones receive smaller files than desktop screens. Use modern formats such as WebP or AVIF where your platform supports them, and serve images from a CDN close to shoppers. Shopify, BigCommerce and Salesforce Commerce Cloud all provide image transformation through their CDNs, so this is often a theme setting rather than new infrastructure.

How do you reduce server response time on product pages?

Time to first byte sets the floor for LCP: nothing renders until the HTML arrives. Cache product page HTML at the edge where your platform allows it, and avoid personalizing the first response when a later request can do it. Recommendations, reviews and recently viewed items can load after the main content. On headless storefronts, check whether server-side rendering is waiting on several API calls before it sends anything.

Which scripts slow product page LCP?

Scripts in the document head that block rendering delay every paint, including the product image. Common culprits on product pages are review widgets, personalization tools, chat, tag managers loading many tags and A/B testing tools. Anti-flicker snippets from testing tools are a special case: they hide the whole page until the test loads, which can push LCP back by seconds, as covered in how to A/B test on Shopify without slowing your site. Defer anything not needed for the first view, load third-party scripts after the main content, and remove apps that no longer earn their place.

Web fonts can also delay text that ends up as the LCP element. Use font-display: swap or optional, preload the one or two font files the product title uses, and avoid loading entire font families for a single weight.

How should you measure LCP on product pages?

Use field data from real shoppers as the source of truth. Lab tools like Lighthouse run one simulated load and are useful for debugging, but they can show a good score while real mobile shoppers on slower networks see a poor one. The difference is explained in Lighthouse vs real-user Core Web Vitals. Group results by page template, so product pages are measured separately from the home page, and by device. Track the 75th percentile after each change rather than the average.

LCP is one of three Core Web Vitals. Once product pages load quickly, check responsiveness too, using the steps in how to improve INP on an ecommerce site, and watch layout shift from late-loading banners and widgets.

Common product page LCP problems and the change that addresses each
ProblemWhat it looks likeChange
Main image lazy-loadedLCP image request starts late in the waterfallRemove lazy loading from the first image, add fetchpriority="high"
Gallery built by JavaScriptImage not in server HTMLRender the first image in HTML; let the carousel enhance it
Oversized imagesLong download for the LCP image on mobileResponsive sizes, WebP or AVIF, CDN delivery
Slow server responseHigh time to first byteEdge caching; move slow lookups off the first response
Page-hiding test snippetBlank page until the test loadsCode-level tests or element-level hiding only

How does Noibu's Performance agent work on LCP?

Noibu's Performance agent measures Core Web Vitals, including LCP, from real shopper traffic. It ranks your worst-performing page groups, so product pages that are slow on mobile surface on their own, identifies the root cause, and stages a change for your review. Nothing goes live until your team approves it. More on the agent is in Noibu's Performance agent.

The Performance agent is one of six supervised agents, alongside Bug Resolution, CRO, ADA, A/B Testing and ROAS. Each runs the same loop of find, build, your approval, ship and measure, in the Noibu console and in AI tools such as Claude through Noibu MCP.

Frequently asked questions

What is a good LCP for a product page?

Google's web.dev guidance treats 2.5 seconds or less as good and more than 4.0 seconds as poor, measured at the 75th percentile of page loads and split by mobile and desktop.

What is usually the LCP element on a product page?

On most product pages it is the main product image in the gallery. On some themes it is a large title block or a promotional banner above the gallery, so confirm the element in your own field data or browser tools.

Should I lazy-load the main product image?

No. Lazy-loading the image that becomes the LCP element tells the browser to wait, which delays LCP. Lazy-load gallery images further down and below-the-fold content instead.

Do apps and third-party scripts affect LCP?

Yes. Render-blocking scripts, A/B testing snippets that hide the page, and apps that inject content above the gallery can all push LCP later. Audit what loads before the main image.

Why is my LCP good in Lighthouse but poor in Search Console?

Lighthouse runs one simulated load on a lab device. Search Console uses real shopper visits on many devices and networks. Field data is what counts for Core Web Vitals, so fix what real shoppers see.

How does Noibu's Performance agent help with LCP?

Noibu's Performance agent measures Core Web Vitals from real shopper traffic, ranks your worst-performing page groups, identifies the root cause and stages a change for your review before anything goes live.

The short version

Product page LCP improves when the main product image is in the HTML, fetched first, right-sized and not held back by render-blocking scripts or a slow server. Measure real shoppers by template and device, and judge progress at the 75th percentile. To see which of your page groups are slowest for real shoppers, start with Noibu's free website audit.

Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.

Back to all blogs
‍
‍
See what Noibu’s AI agents would change on your store first.
Free website audit
Share

Related blog posts

No items found.

Keep your store running at its best, with AI agents that never clock out.