The State of Web Vitals

Image loading attribute

How images load relative to the viewport: eager vs lazy, above vs below the fold, plus CSS backgrounds.

Field data PhoneDesktopAll Scope All sites Q1 2026 edition · Phone field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for Image loading attribute

How images load relative to the viewport: eager vs lazy, above vs below the fold, plus CSS backgrounds.

5
Categories
In the distribution
45.9%
Fleet share
Top: eager_btf
82.9%
Sites with any
Of eager_btf

22.1% of images lazy-load below the fold. 45.9% load eagerly down there.

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv
2

The image loading attribute mix who uses what, and how fast each group loads

Median LCP (sites using feature)
0
0.5s
1s
1.5s
2s
2.5s
3s
3.5s
4s
Eager btf1.6s46% of sites
Lazy btf1.7s22% of sites
Bg1.6s20% of sites
Eager atf1.6s10% of sites
Lazy atf1.6s2% of sites
VariantShare of sitesMedian
Eager btf
46%
1.6s
Lazy btf
22%
1.7s
Bg
20%
1.6s
Eager atf
10%
1.6s
Lazy atf
2%
1.6s

Image loading attribute. On the fleet: 45.9% eager btf, 22.1% lazy btf, 19.6% bg. 82.9% of sites use at least one eager_btf.

Lowest-share bucket: LCP 1.4s. Highest-share bucket: LCP 1.6s. r = +0.35.

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv
3

Passing LCP per bucket every category and count level at once - color is the pass rate

1
2
3
4
5
6
7
8
9
10
11
12
Eager btf 45.9%
84
83
82
81
82
82
82
81
80
79
79
76
Lazy btf 22.1%
84
79
78
80
79
78
79
79
83
82
84
85
Bg 19.6%
84
83
83
82
81
81
80
78
75
73
75
Eager atf 10%
82
81
82
82
82
84
83
84
84
82
82
85
Lazy atf 2.4%
82
81
83
85
85
84
83
85
85
82
83
83
← few of this category on the pagemany →
60%95%+ of sites passing LCP Faded cells: under 100 sites

Each row is a category, each column its own count bucket (few on the left, many on the right); the cell is the share of those sites passing LCP.

Bg swings the hardest: 84% of sites pass LCP with few, 75% with many. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv
4

Few vs many - does quantity cost LCP? the pass rate with few vs many of each category

60%70%80%90%100% few → many
Eager btf 45.9% 84% → 76%
Bg 19.6% 84% → 75%
Lazy atf 2.4% 82% → 83%
Lazy btf 22.1% 84% → 85%
Eager atf 10% 82% → 85%
% of sites passing LCP · hollow ring = pages with few, solid dot = pages with many

Per category: the pass rate among pages with FEW of it (hollow ring) against pages with MANY (solid dot), worst trend first. Thin buckets are excluded from the endpoints.

More Eager btf costs the most: the LCP pass rate falls from 84% with few to 76% with many. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv
5

Why this matters for the Core Web Vitals, and where to start fixing it

Lazy loading is positional. Below the fold it saves bandwidth for content the visitor may never reach. Above the fold it delays pixels the visitor is already waiting for, and on the LCP image it is a direct hit. The same attribute is a win or a bug depending on where it sits.

Read this split with that in mind. Eager below the fold is wasted bandwidth. Lazy above the fold is the bug to fix first. CSS background images follow neither rule: they load when their styles apply, which has its own problems.

How does this affect the Core Web Vitals?

Passing LCP barely moves across the range: 84% at one end, 80% at the other. This signal does not separate passing sites from failing ones.

The split is bigger on INP: 84% pass where Eager BTF is rare, 94% where it is common.

Go fix it Defer offscreen images → Fix: LCP image was lazily loaded → Defer background images →
Related signals Uses @import → Image source mix → DOM size → Page weight & requests → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured