# Your Product Page LCP Is One Image. Find It Before You Optimize Anything

Source: https://edgecommercejournal.com/blog/2026-11-16-product-page-lcp-element-audit.html

November 16, 2026 - Edge Commerce Journal


Published 2026-11-16

A store owner spent two weekends minifying scripts and deferring apps, then checked the score and it had moved by a tenth of a second. The Largest Contentful Paint element on the product page was the same before and after: the main product image, loading late because the browser found it late. That is the usual story. On a Shopify product page, LCP is almost always the hero image, and until that image is discovered early and sized honestly, the rest of the speed work is decoration.

## Name the element before you touch anything

Open the product page in Chrome DevTools, run the Performance panel, and read the LCP element node it reports. No guessing. On most themes it is the first product image inside the gallery. The report also splits LCP into time to first byte, resource load delay, resource load duration, and render delay. Load delay is the silent killer on product pages: the image sits in the page but the browser queues it behind scripts, fonts, and app assets, or waits because the image is swapped in by JavaScript after the gallery initializes. If load delay is the biggest slice, your problem is discovery order, not file size, and compressing the image further will do almost nothing.

## The three fixes that move a product image

First, make the hero image a real image element in the initial HTML with a correct srcset, so the browser can start the download during parsing instead of after a script runs. Themes that lazy-load the first gallery image are a recurring cause of bad LCP; the first image should load eagerly with fetchpriority set to high, while images below it can stay lazy. Second, serve the size the slot actually displays. A 2048-pixel master rendered in a 700-pixel column wastes most of the download on phones, where your p75 visitor sits. Third, check what the image is competing with. A hero video poster, a reviews widget script, and three app embeds in the head all delay the one asset that counts. Harry Roberts at CSS Wizardry has made the same point for years: measure the specific element and its phases before reaching for a general checklist. The general checklist is how a weekend disappears.

## What to ignore until LCP is under control

Total page weight, request counts, and the lab score itself. A product page can carry a heavy analytics stack and still post a fine LCP if the hero image is prioritized, because LCP only times one element. The reverse is also true, and it is the trap: a lean page with a badly discovered hero image fails. Google uses the p75 of real visits, split by device, so test on a mid-range Android profile rather than your desktop on office wifi. Once LCP sits comfortably under roughly 2.5 seconds at p75, further tuning has a poor return, the same floor logic that applies to [checkout friction](https://edgecommercejournal.com/blog/2026-11-13-guest-checkout-vs-forced-account.md): fix the step that is actually losing people, then stop.

## The ten-minute version

Record the LCP element and its four phases on your best-selling product page, on mobile emulation. Fix discovery first if load delay dominates, size second if load duration dominates. Then re-measure the same page. One page, one element, one number that moved or did not. That loop, repeated on the template, is worth more than any app with a speed score in its name.

Keep reading: [The Checkout Auto-Upgrade Already Happened. Here Is What It Broke](https://edgecommercejournal.com/blog/2026-11-15-checkout-extensibility-auto-upgrade-what-broke.md), [Guest Checkout vs Forced Accounts](https://edgecommercejournal.com/blog/2026-11-13-guest-checkout-vs-forced-account.md), and [Abandoned Cart Recovery Timing: Email vs SMS](https://edgecommercejournal.com/blog/2026-11-14-abandoned-cart-recovery-timing-email-sms.md) cover the nearby cases in this series.

## Frequently asked questions

### What is the LCP element on a typical Shopify product page?

Usually the main product image in the gallery. DevTools Performance panel names the exact element, so check there instead of assuming. On some themes it is a hero banner or a large heading block instead.

### Why did compressing my images not improve LCP?

If the biggest LCP phase is load delay, the browser was finding the image late, not downloading it slowly. Compression only shortens load duration. Eager loading, fetchpriority high on the first image, and keeping scripts out of its way fix delay.

### Should the first product image be lazy-loaded?

No. Lazy-loading the LCP image is one of the most common causes of poor product page LCP. Load the first gallery image eagerly and keep lazy loading for the images below it.

### What LCP number should I aim for?

Google treats 2.5 seconds or under at the 75th percentile as good. Measure on mobile, because that is where most stores fail and where most of their traffic sits.
