What the LCP element is on each dealer page
- Homepage: the main banner or featured-vehicle image
- Inventory search page: the first vehicle photo in the list
- Vehicle detail page: the first photo in the gallery
What slows LCP down
| Part | What it is | Usual cause on a dealer site |
|---|---|---|
| Server response | Waiting for the page to start arriving | The page is built from scratch on every visit |
| Found late | Gap before the photo starts downloading | The photo is added by code instead of being in the page |
| Download | The photo itself arriving | A full-size camera photo sent to a phone |
| Paint | Gap before the photo shows | Chat, tracking and other tools busy running |
Where the time should go
Google's guide to LCP describes a page that loads well: nearly all of the time goes to two things, the server response and downloading the photo, and almost none to finding the photo or painting it. If a vehicle page spends most of its time between the photo arriving and the photo showing, other code is in the way, not the photo.
PageSpeed Insights names the LCP element for the page you test and breaks its time into these four parts, so you can see which one is too big.
How to fix a slow LCP
- Never lazy-load the first photo. Lazy loading tells the browser to wait on the one image LCP is measuring.
- Serve photos at the size they're shown. A 3,000-pixel photo in an 800-pixel slot wastes most of its download.
- Put the main photo in the page itself, so the browser finds it right away.
- Let tools load after the photo. Site Speed Engine does this on every page.