FlyingPress uses browser native lazy loading, which defers loading images using the loading="lazy" attribute. However, browsers often preload images before they enter the viewport — sometimes even those far below the fold.
This behavior is intentional and optimized for real user experience, not just synthetic test tools.
Is Lazy Loading Still Working?
Yes. You can confirm it’s working by:
Inspecting image tags: Look for
loading="lazy"Using Chrome DevTools → Performance panel
Running a Lighthouse audit
Even if more images appear loaded, lazy loading is active — browsers are just being smart about when to load them.
Why Do Browsers Preload Lazy Images?
Modern browsers use internal heuristics based on:
Scroll speed
Connection type
Device performance
Image size or importance
For example, Chrome loads images 1250px before viewport on fast connections and 2500px before on slower ones. This helps ensure smooth scrolling and avoids image pop-in delays.
Why Is This Good for Core Web Vitals?
Preloading key images slightly before they’re visible improves Largest Contentful Paint (LCP) and provides a smoother experience for real users, which matters most for Core Web Vitals. Native lazy loading aligns with how users actually browse — not just how test bots score pages.
Why Not Use JavaScript-Based Lazy Loading?
FlyingPress avoids JS-based lazy loading because:
Native lazy loading is faster and more reliable
No extra JS or dependencies
Works even when JS fails or is blocked