Technical SEO
Lazy loading
Lazy loading delays fetching or initializing a resource until it is likely to be needed near the user's viewport.
What it means
Native image and iframe lazy loading can reduce initial network work for below-the-fold content, while code splitting can defer noncritical scripts. The strategy must account for distance thresholds, dimensions, JavaScript availability and whether the resource is part of the initial visible experience.
Why it matters
Deferring offscreen assets can reduce data transfer and competition for critical resources. Applying the same rule to a hero or likely LCP image can make discovery later and worsen the metric the optimization intended to improve.
Example
Product thumbnails below the first viewport use `loading="lazy"`, explicit width and height, while the primary product image loads eagerly and is discoverable in HTML. The page saves initial requests without delaying its main visual or causing layout movement.
Common mistakes
Do not lazy-load the likely LCP image, omit dimensions or hide every image behind interaction-only JavaScript. Avoid loading so many placeholders that the initial document has little height and the browser requests most deferred images immediately.
How AYSA handles this
Signals reviewed
Image position, LCP candidate, loading attribute, intrinsic dimensions, network priority
Problem AYSA can identify
AYSA can find offscreen assets loaded eagerly and critical visible images incorrectly deferred by a global rule.
Recommendation prepared
The proposal assigns eager or lazy behavior per component and includes dimensions and priority only where evidence supports them.
Approval preview
The user reviews affected image roles, viewports and the exact markup changes before approval.
Execution
AYSA can modify approved WordPress image and iframe attributes in supported templates; application components may require developers.
Verification
AYSA checks request timing, LCP selection, layout stability and image availability with representative scrolling and JavaScript conditions.
Limits
Viewport position changes with content and device size, so a universal element-order rule may need template-specific exceptions.
Sources and further reading
- MDN — Lazy loading — Web platform reference
- web.dev — Browser-level image lazy loading — Official Chrome documentation
- web.dev — Performance effects of too much lazy-loading — Official Chrome documentation
Written by Marius Dosinescu. Reviewed by AYSA SEO Editorial Team · 2026-07-28 00:00:00.
Quick answers
Frequently asked questions
Should the main hero image use lazy loading?
Usually not when it is visible immediately or likely to become LCP, because deferred discovery can delay the page's primary content.
SEO execution campaign
Less SEO work. More organic growth.
AYSA monitors your website, finds opportunities, prepares the work, asks for approval and executes accepted changes so you can grow without living in SEO tools.
