Separate image, server and resource-loading delays to prioritise work on the main content users see when opening a page.
Chasing one performance score can hide the actual visitor problem. Identify which page is slow and under what conditions. A quick home page does not establish that product pages or mobile visits are equally quick.
Understand LCP
Largest Contentful Paint measures when the largest eligible visible image or text block is rendered. Web.dev identifies 2.5 seconds or less at the 75th percentile as a good target. Distinguish lab tests from real-user measurements.
Locate the delay
Determine whether the server responds slowly, the main image is discovered late or rendering is delayed after download. These problems need different fixes. Removing resources blindly can break functionality.
Avoid delaying the main image
Lazy-loading an above-the-fold LCP image can delay its appearance. Review dimensions, compression and loading order together. Do not automatically apply below-the-fold image settings to the primary image.
Compare equivalent conditions
Retest the same page with similar device and network settings. Verify image quality, navigation and forms as well. Use repeated measurements and real-user data when available rather than relying on one good run.