> Regarding lazily loading CSS background images, Chromium determines whether
> or not to lazily load CSS background images according to the default lazy
> loading behavior, and isn't directly controlled by the "loading" attribute.
> There are some heuristics involved, e.g. background images inside an iframe
> that was itself lazily loaded are loaded eagerly for performance reasons,
> but those heuristics are just part of the default lazy loading behavior.

Scott, thanks for the clarification! Are there plans to better specify CSS background images lazy loading?

Regards,

Rob.