Lazy loading defers an image, iframe, or other resource until it is about to enter the visible viewport, so the browser fetches it only as the reader scrolls toward it rather than all at once when the page first loads.
| Term | Lazy Loading |
|---|---|
| Category | Structured Data, Social and Media |
| Also known as | Lazy Load |
| Where it appears | Media and performance factors |
What it means in RankGear
Lazy loading turns up among RankGear’s media and performance factors, where the app looks at how a page delivers its images and embedded resources. When it checks a page, RankGear can detect whether media below the initial view is deferred — typically through a loading="lazy" attribute or an equivalent script-driven technique — instead of being pulled down in full before anything renders. It is a property of how the page is built, not a rating of the media itself: the factor records whether the deferral is present and applied to the resources where it makes sense, so a heavily illustrated page that loads its off-screen images on demand reads differently from one that requests every asset up front.
How to interpret it
Read this factor by checking where the deferral is actually applied, not just whether the page uses it somewhere. The signal is most useful for content that sits well below the fold — long galleries, embedded video, images near the end of a long article — and least appropriate for anything in the first screen a reader sees, where deferring a hero image can delay the very content you want to appear fastest. Treat it as one comparative input alongside the rest of the media and performance factors: RankGear is describing how ranking pages in your set handle media loading and whether your page follows or departs from that pattern, not assigning a performance grade the way a lab tool would.
Example
You are analyzing a photo-rich buying guide against the pages ranking for the same query. RankGear’s media factors show that most of the competitive set defers its lower images with loading="lazy" while eagerly loading the hero shot, and that your page instead requests all two dozen images on load. The report flags the gap: the ranking pages front-load only what the reader sees first and defer the rest, so you can mirror that pattern by adding lazy loading to the off-screen media while leaving the top image to load immediately.
Important considerations
- Lazy loading suits below-the-fold media; applying it to first-screen or hero images can slow the content readers see first, so where it is used matters as much as whether it is used.
- The factor confirms the technique is present on the page — it does not measure the actual load time or the perceived speed a visitor experiences, which depend on hosting, image weight, and the device.
- Whether ranking pages share a media-loading pattern is a correlation with what currently ranks for your query, not proof that lazy loading caused those positions or that adding it will move yours.
- Media and performance factors are comparative indicators of how your page differs from the competitive set, not scores Google assigns to the page.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.