Somebody sees a truck they like. They tap the listing while standing in a parking lot on mobile data.
The page starts loading. First a header. Then a spinner where the photos should be. Then more spinner.
They go back and tap the next dealer.
That shopper was ready. They had intent, they had the phone in their hand, and they never saw your vehicle.
Why this hits car lots harder than most businesses
The product is photos. Nobody buys a used vehicle without seeing twenty pictures of it. Which means your listing pages are the heaviest pages you have, and they are the ones that matter most.
The ticket is enormous. A lost visitor at a coffee shop is a few dollars. A lost visitor here might have been a unit. The math scales accordingly.
Shoppers are comparing in real time. They have four tabs open on the same body style. Whoever loads first gets looked at first, and often gets the call.
They are on their phone, away from wifi. On the lot, at work, in somebody else's driveway. That is the connection that matters, and it is not the one your office tests on.
Price out what the delay costs
Traffic, load time, conversion rate and what a sale is worth. On a high-ticket item like a vehicle, a small percentage of lost visitors turns into a large number very quickly.
Your numbers
What that means
Most of this is images that were never resized, a page builder, and six plugins doing one job. It is fixable in an afternoon by somebody who knows where to look.
The retention curve here is a working model of well-documented mobile abandonment behavior, not a measurement of your site. Run PageSpeed Insights for your real numbers.
What this assumed
- Uses a conversion penalty that grows with load time. Your real curve depends on your audience and your offer.
Runs in your browser. Nothing you type is sent anywhere.
This is an estimate
This tool returns an estimate based on the numbers you entered. Your real result depends on your own costs, rates and conditions. Check it against your own records before you make a decision with it.
How to run it, step by step
- 1Get your real load time on a phone. Test on mobile data, not on the office wifi. Most of your shoppers are on a phone in a parking lot somewhere, and that is the experience that decides whether they wait.
- 2Use your actual monthly traffic. From your analytics, not an estimate. Inventory pages specifically if you can separate them, because that is where the buying happens.
- 3Put in your real lead conversion rate. The share of visitors who fill in a form, call, or start a finance application. Most lots know units sold and have never worked this one out.
- 4Use gross per unit, not sale price. What you actually make on an average unit including any back end. That is what a lost shopper is worth, and it is what makes this math get big.
How to read what it gives you
- The number is an estimate built on your inputs, not a promise. Use it to decide whether speed is worth attention, not as a forecast.
- Vehicle photos are almost always the cause. Twenty full resolution images on a listing page will bring any site to a crawl on mobile data.
- Compare the annual figure to what fixing it would cost. On a high-ticket item, one recovered unit often covers the entire fix.
The tool is free, it does not expire, and you can put it on your own website if you want it there. Nothing on this page is locked.
Not ready to talk? Browse the rest of the free tools
The fix is nearly always the photos
Before anybody sells you a rebuild, check the images.
Size them for the web. A photo straight off a camera can be several megabytes. The same photo correctly sized for a phone screen is a fraction of that and looks identical to the shopper. Thirty photos at full size is a page nobody waits for.
Compress them. Modern formats do this well and the quality difference is invisible on a phone.
Load them lazily. Show the first few images immediately and load the rest as the shopper scrolls. Most never scroll to photo twenty-eight anyway.
Do those three and most dealer sites get dramatically faster without changing anything else.
Then the scripts
Open your site and count the third-party tools loading on it. Chat widget, trade-in valuation, finance calculator, two analytics tools, a heat map tool somebody installed in 2023, a pixel for an ad account you no longer run.
Every one of those is a request the browser makes before the page finishes. Remove the ones nobody uses. In most cases that is more than half.
Test it honestly
Go stand at the far side of your own lot with your phone on cellular data, turn off wifi, and load a vehicle detail page.
Count the seconds. Ask yourself whether you would have waited if you were not the owner.
That is the whole diagnostic, and it is more useful than any report, because it is exactly the moment where you are winning or losing the shopper.
Questions people actually ask
What usually makes a dealer site slow?
Photos, by a mile. Twenty or thirty full resolution images per vehicle, uploaded straight off a camera or a phone, served at full size to a mobile browser. After that it is usually a stack of third-party scripts: chat widgets, trade valuation tools, tracking pixels and inventory feeds all loading at once.
How fast should it be?
Fast enough that a shopper on mobile data sees the vehicle before they lose patience. Rather than chasing a target number, test your own site on a phone away from the lot and be honest about whether you would have waited.
Can I fix this without rebuilding the site?
Usually a large part of it, yes. Compressing and correctly sizing vehicle photos, lazy loading images below the fold, and removing scripts nobody uses will fix most dealer sites without touching the platform.
What if my inventory site is provided by a vendor?
You still control the photos you upload, which is most of the problem. Beyond that, put the speed question to your vendor directly and ask what they can change. It is a reasonable thing to expect from a platform you pay for.