A Quick Way to Fix LCP: Four Changes That Cut Time to Paint

Largest Contentful Paint fails when the browser is still waiting on the server, fighting for bandwidth, or blocked on JavaScript before it can paint the biggest thing in the viewport. You do not need a six-week programme to move a red LCP. In delivery work, four changes cover most urgent regressions.

Start with Time to First Byte: cache queries, HTML at the edge, and generated code paths so the first byte arrives sooner. Then clear the path to the LCP element. Icons, third-party scripts, below-the-fold images, and non-critical fonts should enqueue after the LCP resource, not ahead of it.

Mark the single LCP candidate with fetchpriority="high" (and preload when the hero is known at build time but late in markup). Finally, schedule low-value JavaScript after the load event so the main thread can paint once the asset arrives.

• Cut TTFB with object cache, CDN HTML cache, and opcode or template caches before you resize heroes.

• Defer icons, analytics, lazy below-fold images, and secondary fonts until after the LCP request starts.

• Set fetchpriority="high" on the one LCP element PSI reports; do not mark every image high.

• Run heatmaps, chat, and secondary widgets after load (requestIdleCallback where supported).

Re-test the same URL after each change. Scheduled lab runs catch the next theme or tag deploy that puts competing work back on the critical path.

Read more: how to improve LCP with four paint fixes