[acdha]

This is covered in the part about the “calculated distance” where they describe the logic used to load the images in the current implementation: it loads before use but waits until the images are near the viewport.

There's an FAQ about carousels, too:

https://web.dev/native-lazy-loading#how-does-the-loading-att...

> How does the loading attribute work with images that are in the viewport but not immediately visible (for example, behind a carousel)? > > Only images that are below the device viewport by the calculated distance load lazily. All images above the viewport, regardless of whether they're immediately visible, load normally.