Troubleshooting common issues with Optimize LCP Images within Jetpack Boost

If Jetpack Boost is not optimizing your Largest Contentful Paint (LCP) images as expected, this guide helps you identify common issues and resolve them, including specific LCP analysis errors such as HttpError, LcpTimeout, and page-navigated.

Pages not being optimized

Check page availability

Confirm that Jetpack Boost can reach the pages you want optimized:

• Ensure your important pages are publicly available, and not password protected.
• Verify pages return a 2XX HTTP response (not 404 or server errors).

Review page structure

The layout of a page affects how reliably Boost can detect the LCP element:

• Pages with one clear, prominent visual element work best.
• Multiple competing large images can complicate LCP detection.
• Very complex layouts may require manual optimization.

Optimization results not visible

Clear caches

Cached versions of a page can hide the optimizations Boost applied. Clear each cache in turn:

• Clear your site’s page cache.
• Clear the CDN cache if applicable.
• Test in a private or incognito browser window.

Verify implementation

On a Cornerstone Page, view the page source and look for the following attributes:

• fetchpriority="high" on optimized images.
• loading="eager" instead of lazy loading.
• data-jp-lcp-optimized="true"

Specific error types

When Boost cannot measure a page’s LCP, it reports one of the following error types. Each section explains the cause and the steps you can take to resolve it.

HttpError

Cause

The page failed to fully load within 60 seconds — often due to slow server response or large, complex pages.

Solution

Take the following steps to help the page load reliably:

• Check your hosting performance and server logs.
• Make sure the page loads quickly and reliably.
• Test with a lighter version of the page.

LcpTimeout

Cause

Jetpack Boost could not reach the page due to a network or HTTP error — usually caused by timeouts, firewalls, or unstable connections.

Solution

Confirm that Jetpack can reach and load the page:

• Verify the page loads consistently and returns a valid response (2XX HTTP code).
• Ensure your hosting provider allows external services like Jetpack to access your site.
• Temporarily disable security or firewall rules that may block Jetpack.

LcpMetricTimeoutError

Cause

Jetpack Boost loaded the page successfully, but could not detect the Largest Contentful Paint element within 60 seconds. This can be caused by pages with slow-loading content, or dynamic content that never stabilizes.

Solution

Make sure the page presents stable visual content that Boost can measure:

• Ensure the page has visual content that loads within a reasonable timeframe.
• Check for JavaScript errors or infinite loading states that prevent content from stabilizing.
• Verify the page isn’t primarily empty, redirect-heavy, or composed entirely of dynamically-loaded content.

ElementNotUnique

Cause

Jetpack Boost detected multiple large visual elements and could not determine which one should be optimized as the LCP.

Solution

Help Boost identify a single dominant element:

• Simplify your layout or ensure there’s one clearly dominant visual near the top of the page.
• Avoid having multiple competing hero images or background sections above the fold.

ElementNotStable

Cause

Jetpack Boost identified a potential Largest Contentful Paint element, but it did not remain consistently visible for several seconds during analysis. This often occurs with carousels or auto-rotating sliders, animated hero sections, or components that quickly swap, fade, or slide content after load.

Solution

Keep the LCP element visible long enough for Boost to measure it:

• Keep the hero/LCP element visible for at least 3 seconds during initial load (for example, pause or delay autoplay/rotation).
• Set the slider to start on the hero slide and delay the first transition (3 seconds or more).
• Minimize heavy entrance animations that immediately replace the hero content.
• If you cannot make these changes yourself (for example, using a theme or slider plugin without settings):
  • Contact the theme or slider plugin authors and request that their carousel respects prefers-reduced-motion: reduce (pause or disable autoplay and transitions when users prefer reduced motion).
  • Ask for a setting to disable or delay autoplay on initial load so the main slide remains visible long enough for analysis.

page-navigated

Cause

The page redirected to another URL during analysis, so Jetpack Boost could not measure its LCP. When the cloud reports the redirect target, Boost shows it as the final URL in the error message. Common causes include canonical redirects, trailing slash redirects, locale redirects, and geo redirects, as well as login walls.

Solution

Resolve the redirect so Boost analyzes a page that loads directly. Choose one of the following:

• Remove the URL from your Cornerstone Pages.
• Point the Cornerstone Pages entry at the final destination URL.
• Remove the redirect so the page loads without redirecting.

Unknown

Cause

Jetpack Boost was unable to determine the cause of the issue during analysis.

Solution

Wait a few minutes and try the analysis again.

Still need help?

If you still need assistance, contact support. We are happy to advise.