# The Hero Image Fix: Eager Loading, fetchpriority, and One Priority Per Page

Source: https://storefrontspeedjournal.com/blog/2026-11-17-hero-image-fetchpriority-lcp-fix.html

Reviewed November 17, 2026


Open your theme and check the hero image tag. If it carries loading lazy, that is your first fix: the Largest Contentful Paint image should load eager with fetchpriority set to high, which tells the browser to start it before layout finishes guessing priorities. Shopify's image\_tag filter accepts both attributes directly, and its documentation recommends fetchpriority high on the LCP image to remove the discovery wait. Use high priority on one image per page. Marking five images high priority is the same as marking none, because priority is a ranking, not a sticker.

## Why the browser gets the hero wrong by default

By default the browser discovers images at low priority and raises the important ones after layout, when it knows what is in the viewport. For a hero image that is the largest thing on the page, that delay is pure waste: the file that decides LCP waits in line behind resources that do not. fetchpriority high skips the guessing stage. In Google's published tests, adding it to the LCP image cut LCP by roughly 5 to 30 percent depending on how late the image was being discovered.

Lazy loading makes the same wound deeper. A lazy hero does not even enter the queue until the browser calculates it is near the viewport, which for the first screen is a delay with no benefit at all. Themes and image apps apply lazy loading globally because it helps long pages of below fold images, and then the setting quietly taxes the one image that matters most.

## The Liquid change, and the preload question

With Shopify's image\_tag filter, the pattern is to pass loading eager and fetchpriority high for the first section's image and lazy for later sections, which the filter supports directly and which theme code often keys off the section index. If your hero is rendered by an older template or a custom section, the equivalent plain HTML attributes do the same job: loading="eager" and fetchpriority="high" on the img tag, with width and height present so layout does not shift while it loads.

Preload is a different tool for a narrower problem. A preload link tells the browser to fetch a file it would otherwise discover late, such as a hero delivered as a CSS background or injected by a slider script. If the image is a normal img in the HTML, the preload scanner already finds it early and fetchpriority is the right lever. Preloading everything is the classic overcorrection: Shopify's guidance is to preload one or two late discovered resources, and every extra preload competes with the hero for the same bandwidth.

## Verify the fix where it counts

Re run PageSpeed Insights and read the LCP breakdown again, specifically the resource load delay segment, which is the part this fix attacks. If load delay shrinks and total LCP barely moves, the bottleneck was never discovery: look at the file's load duration (too many kilobytes) or its render delay (blocked by scripts or fonts) instead, and do not keep polishing the priority attribute.

Then check the field data over the following 28 days rather than declaring victory on one lab run. Lab tests are for diagnosis. The 75th percentile of real visits is the grade, and it moves slowly because it is a rolling window. A fix that survives the field window is a fix. Everything before that is a promising lab result, and this journal has buried enough of those to know the difference.

## Related reading

Related reading on this site: [Unused CSS in Shopify Themes: Finding the Styles Your Pages Load and Never Use](https://storefrontspeedjournal.com/blog/2026-11-16-unused-css-shopify-theme-audit.md), [Your Store Is Not Slow on Your Phone: Testing on the Mid Range Device Your Customers Use](https://storefrontspeedjournal.com/blog/2026-11-16-speed-test-mid-range-phone-throttling.md).

## Frequently asked questions

### Should my hero image be lazy loaded?

No. Lazy loading delays the image until the browser decides it is near the viewport, which for the first screen image is a pointless delay on the element that decides LCP. The hero gets loading eager. Lazy loading belongs on below fold images, where it genuinely helps.

### What does fetchpriority high actually do?

It tells the browser this image matters before layout finishes, so the download starts at high priority instead of being upgraded later. On an LCP image that removes the resource load delay. Use it on one image per page, since priority is a ranking and marking everything high marks nothing.

### Do I need a preload tag as well as fetchpriority?

Usually not for a normal img tag, which the browser's preload scanner finds early on its own. Preload earns its place when the hero is discovered late, such as a CSS background image or a script injected slider image. Preload one or two late resources at most, or the preloads compete with the hero itself.

### How do I know the fetchpriority fix worked?

Compare the LCP breakdown in PageSpeed Insights before and after: the resource load delay segment should shrink. Then watch field data over the next 28 days, since the 75th percentile of real visits is the metric that counts and it updates as a rolling window.
