Image field binding and responsive output
Check the loading setting on the concrete image element or its template. Images in the first visible area should not be delayed out of habit.
Compare the image and alt text binding in the collection template with the specific item. An empty alternative text may be due to missing content data, while an overly large file is created by the selected output.
Where to check the setting in Webflow
Control the image source and the alt text of the concrete element, in the case of CMS content also its field binding. After that, check the actually loaded responsive image variant. An empty collection value can affect several otherwise correctly constructed image instances.
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 Webflow
Check a completely and an incompletely maintained item on a narrow screen. Check loaded variant, reserved area and text alternative separately.
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.
Reference: Websites published on Webflow and CMS Collections. Exported HTML or an upstream own proxy layer may have other responsibilities.
Classify the general error
Definition, system-independent causes and further correction examples: Judge images by their position in the first screen