Case Studies FetchPriority Featured Image: a faster LCP
FetchPriority Featured Image: a faster LCP
TL;DR The featured image is often the Largest Contentful Paint element, but the browser does not know it is important and may load it late. Adding fetchpriority high tells the browser to fetch it first. This plugin sets that attribute on the featured image so LCP lands sooner.
Largest Contentful Paint measures when the biggest visible thing finishes loading. On a lot of WordPress sites, that biggest thing is the post's featured image. The catch is that the browser does not automatically know the featured image is the star of the page, so it can end up loading late behind other resources. This plugin fixes that with a single attribute.
The problem
When a browser parses a page, it discovers resources and schedules them. Images generally get a lower priority than scripts and stylesheets, and the browser only learns which image is the largest once it has laid the page out. By then, your featured image might already be stuck behind a queue of less important downloads.
The result is a slower LCP than the image size alone would suggest. The bytes are not the problem; the ordering is.
The approach
There is a purpose-built hint for this: fetchpriority="high". Put it on the element that is your LCP, and the browser fetches it sooner.
The discipline is to use it on exactly one element. Priority is relative, so if you flag many images as high, none of them really is. The featured image is almost always the right and only target.
What shipped
The plugin adds fetchpriority="high" to the featured image markup. No settings to fuss with, no risk of over-applying it across the page. The browser gets a clear signal about which image to fetch first, and on image-led layouts LCP improves because the largest element stops waiting its turn.
What I learned building it
The lesson was restraint. It would have been easy to add priority hints in more places and claim a bigger feature, but that would have diluted the very signal the plugin exists to send. A good performance tweak often does less, not more. One attribute, on the one element that matters, is the whole point.
Pair this with keeping the main thread free, and you cover two of the three Core Web Vitals. For the interaction side, see my notes on fixing INP and QueueForge. FetchPriority Featured Image is free on WordPress.org.
FAQ
What does fetchpriority high do?
It is a hint that tells the browser to prioritise fetching a resource. On the LCP image, it moves the fetch up the queue so the largest visible element paints sooner, which is what the LCP metric measures.
Won't the browser figure out the important image on its own?
Sometimes, but not reliably. Browsers discover images as they parse and lay out the page, and the featured image can lose the race to less important resources. An explicit priority hint removes the guesswork for the element that matters most.
Can fetchpriority high hurt performance if overused?
Yes. Marking everything as high priority is the same as marking nothing, and it can starve genuinely urgent resources. The point is to apply it to the one LCP element, which is why the plugin targets the featured image specifically.