Which photos to lazy-load
| Page | Load right away | Lazy-load |
|---|---|---|
| Vehicle detail page | The first gallery photo | Every other gallery photo |
| Inventory search page | The first row of vehicle cards | Cards further down the list |
| Homepage | The main banner | Offers and cards below the first screen |
How lazy loading works
Modern browsers support it with one setting on the image: loading="lazy". The browser then fetches the image when it's close to coming into view. Google's guidance is to leave it off any image likely to be in the first screen.
Every lazy-loaded photo also needs its width and height set, so the space is held while it arrives. Without that, the page jumps when the photo lands, which counts against Cumulative Layout Shift.
Size photos for the screen
Lazy loading decides when a photo downloads; size decides how long it takes. A photo taken at full camera size and shown in a phone-sized slot wastes most of its download. Serve each photo at the size it's shown, in a modern format such as WebP or AVIF where the platform supports it.
How to check it's working
- 1
Run a vehicle page through PageSpeed Insights
Look for warnings about offscreen images and properly sized images.
- 2
Check the LCP element
The report names it. If it's the first vehicle photo and it's lazy-loaded, remove lazy loading from that one image.
- 3
Watch the gallery on a phone
Swipe through. Photos should appear as you reach them, without the page jumping.
Photos first, tools after
Even a well-sized first photo waits if chat and tracking tools are starting up at the same time. Site Speed Engine lets those tools load after the photo and price, on every vehicle page. More on vehicle detail page speed.