Media library and concrete image instance
An integrated third-party embed or own theme image does not necessarily use the same loading strategy as a standard image block. Treat the main visible image separately.
The alt text in the media library does not have to be the only value: a block or builder can store its own text and image size. Therefore, examine the image used in the article and the delivered img edition.
Where to check the setting in WordPress
Select the specific image instance in the article and compare its alt text with the data set in the media library. For own PHP output, wp_get_attachment_image can provide sizes and responsive sources; a hard-coded img tag does not automatically use this output.
Example of this specific finding
Illustrative control case: Twenty images far below the first visible area load immediately. The large visible hero image, on the other hand, does not belong in the same delay rule.
follow-up audit in WordPress
After correcting image URL, check alternative text and selected responsive variant. A global media change does not use as proof that all existing blocks have been updated.
Suitable downstream images are loaded delayed and checked in the network protocol when scrolling. Continue to request visible key images in time.
Derogations and scope
Lack of lazy loading on the LCP image is often intentional. A blanket rule for all images can worsen the visible loading time.
Related: WordPress with classic or block theme. SEO plugins and page builders are different; there is no universal menu path for all installations.
Classify the general error
Definition, system-independent causes and further correction examples: Judge images by their position in the first screen
Configuration and test signal documentation
WordPress: Image output with sizes and attributes