Lazy Load Savings Calculator
Estimate how many KB/MB lazy loading saves on initial page load based on your image count, size, and user scroll behavior.
Page Image Settings
Adjust the values to match your page.
0%100%
0%100%
Results
Total payload (before)
—
Bytes saved (lazy load)
—
Savings percentage
—
Images never loaded
—
Estimated LCP improvement (3G)
—
Rough estimate: ~100 ms per 100 KB saved on a 3G connection (~1.5 Mbps). Actual results vary by network, CDN, and which image is your LCP element.
Calculation breakdown
Summary
Estimate how many KB/MB lazy loading saves on initial page load based on your image count, size, and user scroll behavior.
How it works
- Total payload is computed as image count multiplied by average image size.
- Below-the-fold image count is total images times the below-fold percentage.
- Never-loaded images equals below-fold count times the never-scroll percentage.
- Bytes saved equals never-loaded images times average image size.
- LCP improvement is estimated at roughly 100 ms per 100 KB saved on a 3G connection.
Use cases
- Justify adding lazy loading to a content-heavy blog or news site.
- Estimate performance gains before implementing lazy loading in a web app.
- Quickly compare lazy load impact across different page layouts.
- Support a Core Web Vitals improvement proposal with concrete numbers.
Frequently Asked Questions
Last updated: 2026-07-01 ·
Reviewed by Nham Vu