Forty-two of 50 dealer websites had at least two mobile errors. The most common problem appeared on 38 sites. The most damaging one blocked the call button before the shopper finished viewing the first screen.
We audited 50 dealer websites on an iPhone 14.
The sample included 25 franchise stores and 25 independent dealerships. We checked each site in Safari, ran Google PageSpeed Insights in mobile mode, tested the primary CTA with one thumb and reviewed available call-tracking patterns.
Forty-two sites had at least two of the five errors.
Thirty-four sites opened a pop-up within five seconds. Thirty-one let the call button disappear after scrolling. Twenty-eight had weak photo delivery or slow mobile performance.
The combined modeled call gap reached 15%.
The five individual call-loss estimates total more than 15% because the problems overlap. A site with an early pop-up often had a hidden call button and weak contrast too. Adding every percentage would count the same lost caller several times.
This was a 50-site operational audit, not a nationally representative study. The findings show what appeared in this sample and what digital managers should test on their own VDPs.
| # | Mobile Error Found in the 50-Site Audit | Sites Affected | Modeled Call Impact | What We Saw on Mobile | Why Calls Suffered | Send This Fix to Your Vendor |
| 1 | Pop-up blocks the call button within five seconds | 34 of 50, or 68% | Up to 8.1% | Get ePrice overlay covers most of the screen and sticky bar | Shopper must close a form before calling | Delay overlay for 25 seconds or meaningful engagement |
| 2 | No sticky call bar | 31 of 50, or 62% | Up to 4.2% | Call button appears near the top, then scrolls away | Primary action disappears during VDP research | Add a fixed Call, Text and Directions bar |
| 3 | Weak photo delivery or slow mobile load | 28 of 50, or 56% | Up to 1.8% of calls plus VDP loss | Blank image boxes, delayed galleries and low PageSpeed scores | Shopper waits before seeing enough condition detail | Load the first six images quickly and defer the rest |
| 4 | Lead form appears before call action | 26 of 50, or 52% | Up to 2.4% | Large form fills the first screen, Call sits below it | Form friction interrupts high-intent shoppers | Put Call first and the form second |
| 5 | Low-contrast call button | 38 of 50, or 76% | Up to 1.5% | Thin white outline blends into the background | Shopper misses the primary action | Use a solid, high-contrast button with a large tap area |
Call impacts represent directional estimates from the supplied call-tracking comparison and prior CTA tests. They do not prove each design problem caused the full loss on every website.
#1: Early Pop-Ups Blocked Calls on 34 of 50 Sites
This was the worst error in the audit.
Thirty-four sites opened a form between page load and the fifth second. Most asked the shopper to unlock a price, claim an offer or confirm availability.
The overlay often covered 60% to 70% of the mobile screen. On several sites, the sticky call bar remained visible behind the pop-up but did not respond until the shopper closed the overlay.
The close icon created another problem. It sat near the top-right corner and used a small tap area. A shopper holding the phone with one hand had to reach, close the form and return to the original task.
Screenshot description:
A mobile VDP with a Get Your ePrice form covering the vehicle photo, price and bottom call bar. A small X appears in the top-right corner. The Call button remains visible behind the dark overlay but cannot be selected.
Do not interpret “zero calls during the first five seconds” as proof of an 8.1% loss. Few buyers call within five seconds under any design. The stronger evidence came from lower tracked call rates on sessions exposed to the early interruption and prior tests where delayed overlays performed better.
A better trigger uses engagement:
25 seconds on the VDP
Two meaningful scrolls
Six or more gallery images viewed
A return visit to the same vehicle
Mobile exit intent is unreliable because phones lack desktop cursor behavior. A time or engagement trigger gives the shopper room to inspect the vehicle first.
Action: Send your vendor this request: “Remove every mobile overlay opening within five seconds. Delay the form for 25 seconds and suppress it after Call, Text or Directions is selected.”
#2: The Call Button Disappeared on 31 Sites
Thirty-one websites placed the main call action near the top of the VDP without keeping it visible.
The button appeared beside the price or below the vehicle title. After the shopper viewed photos and scrolled through features, the action disappeared two or three screens above.
Calling required the shopper to stop researching, scroll back and locate the button again.
Screenshot description:
Left side shows a VDP after two screens of scrolling. No call action remains visible. Right side shows a fixed bottom bar with Call, Text and Directions within thumb reach.
The comparison associated sticky mobile controls with a call-rate advantage up to 4.2%. The result matches a simple usability principle. Important actions work better when shoppers see them at the decision point.
A sticky bar should remain compact. An oversized bar steals screen space and might cover pricing, disclosures or form controls.
Use three actions at most:
Call
Text
Directions
Make Call the most prominent when phone conversion is the primary KPI. Pass the vehicle stock number into the call-tracking record when the platform supports it.
Action: Ask your vendor for a fixed bottom action bar on every mobile VDP. Test the bar at the top, middle and bottom of the page before approval.
#3: Photo and Speed Problems Appeared on 28 Sites
Twenty-eight sites showed one of two problems:
Fewer than six usable photos appeared during the test, or the gallery loaded slowly enough to interrupt browsing.
Several pages displayed blank gray image boxes. Others loaded one image at a time as the shopper swiped. A few VDPs carried large image files without effective resizing or deferred loading.
Screenshot description:
The first panel shows a PageSpeed mobile score of 42. The second shows a VDP gallery with two loaded photos followed by blank placeholders.
PageSpeed Insights does not run on an iPhone 14. It uses a separate mobile testing environment. We used the iPhone for manual behavior and PageSpeed Insights for an independent lab measurement.
Do not use a three-second rule as the only pass or fail standard. Current Core Web Vitals guidance treats Largest Contentful Paint of 2.5 seconds or less as good when measured at the 75th percentile. Google web.dev guidance on LCP
For the VDP, the practical goal is more specific. The hero image, vehicle title, price and primary CTA should become useful before the entire 20-photo gallery finishes loading.
Use this sequence:
Load the hero image first
Prioritize the next five images
Resize files for mobile delivery
Defer images farther down the gallery
Reserve image dimensions to prevent page movement
Remove broken and duplicate URLs
Twenty photos do not help when the first six arrive late. Photo quantity and delivery speed need separate checks.
Action: Test five high-traffic VDPs in PageSpeed Insights and on a real phone. Record LCP, gallery load behavior, broken images and the number of usable photos visible within the first browsing session.
#4: Forms Pushed Call Below the Fold on 26 Sites
Twenty-six sites placed a large lead form near the top of the mobile VDP.
The shopper saw fields for name, email, phone and ZIP code before reaching the phone action. On some pages, the form occupied the entire first screen below the vehicle photo.
Screenshot description:
A Get ePrice form fills the area below the vehicle title. The Call button sits beneath the form and requires another scroll.
A form-first layout assumes every mobile visitor wants to submit data. Call-tracking behavior showed a different path for high-intent shoppers. Some wanted one answer from a salesperson before giving contact information.
The isolated CTA comparison associated a call-first layout with up to 2.4% more calls.
Keep the form. Change the order.
Recommended mobile hierarchy:
Vehicle and price
Primary Call action
Check Availability action
Short lead form
Details, options and disclosures
Do not force a form before displaying the dealership number. Also avoid click-to-call buttons routed through a general line where nobody knows which vehicle prompted the call.
Action: Tell your vendor: “Move the primary Call button above the lead form on mobile VDPs. Keep the form available below the first action block.”
#5: Low-Contrast Call Buttons Appeared on 38 Sites
This was the most common finding.
Thirty-eight sites used a call button with weak contrast, thin borders or styling too similar to surrounding controls. White outline buttons often disappeared against white or light-gray backgrounds.
Screenshot description:
The first VDP shows a thin white Call outline against a pale background. The comparison uses a solid green button with white text and a phone icon.
Green performed well in the supplied CTA test, but green is not a universal conversion rule. A green button fails when the site already uses green across headers, badges and secondary actions.
Contrast and hierarchy matter more than one color.
The call action should:
Stand apart from nearby buttons
Use readable text contrast
Include a clear phone icon
Provide enough height for thumb use
Remain visible in bright outdoor light
Show a clear pressed or selected state
WCAG 2.2 sets a minimum target-size criterion of 24 by 24 CSS pixels, subject to listed exceptions. A 44-pixel button height gives the store a more forgiving internal mobile standard. W3C guidance on target size
The audit associated low-contrast controls with up to a 1.5% call gap. Run a controlled test before applying the same color across every site.
Action: Replace the outline treatment with one solid, high-contrast call button. Keep placement and wording unchanged during the design test.
How We Ran the 50-Site Audit
The sample included 25 franchise dealership websites and 25 independent dealership websites selected across major U.S. markets.
Each site received the same core review:
iPhone 14 with Safari
Mobile home page and one active VDP
Manual thumb-reach test
Call-button visibility after scrolling
Pop-up timing
Lead-form position
Photo count and gallery behavior
Google PageSpeed Insights mobile test
Seven-day call-tracking review where comparable data was available
Screenshots of each observed error
The full review took about eight hours.
The thumb test asked one question: Could a shopper reach and select Call without changing grip, stretching across the screen or scrolling back to the top?
Each error received a yes or no value.
The research has limits. Fifty sites do not represent every dealership platform. Traffic sources, inventory, pricing, store hours and call handling also affect call volume. The audit identified strong operational patterns, not a controlled national experiment.
Replicate the review with ten of your highest-traffic VDPs. Use a second set of ten after the vendor publishes fixes.
Track:
Mobile VDP sessions
Call-button taps
Connected calls
Calls over 30 seconds
Appointments
Shows
Sold customers
Button clicks alone do not prove improvement.
Digital Math: A 15% Call Gap Reaches $35,640 Before a Conservative Adjustment
Start with 60 mobile calls per day.
A 15% recoverable gap equals:
60 × 15% = 9 calls per day
Move those calls through the supplied sales funnel:
9 calls × 30% appointment rate = 2.7 appointments
2.7 × 50% show rate = 1.35 shows
1.35 × 40% close rate = 0.54 sales per day
At $2,200 total gross:
0.54 × $2,200 = $1,188 per day
Across 30 days:
$1,188 × 30 = $35,640
The $35,640 figure assumes every recovered call is unique, connected, qualified and incremental. Real call data includes repeat callers, missed connections, existing customers and sessions where the shopper would have called through another route.
Apply a 47% haircut for duplication and uncertain incrementality:
$35,640 × 53% = $18,889.20
Rounded conservative model:
$19,000 in monthly gross
Do not subtract an unspecified “vendor fix cost” to force the total down. Price the development work separately, then calculate payback from verified incremental sales.
Your Monday website report should show:
Sites or templates with each error
Mobile VDP sessions
Call conversion rate
Connected-call rate
Appointments from mobile calls
Sales from mobile calls
Date each fix went live
Forty-two of 50 websites failed at least two checks. Most fixes did not require a redesign. They required removing an interruption, keeping Call visible, loading useful content sooner and making the primary action easier to select.
Related: 9 Mobile CTA Tests That Generate 15% More Calls
Related: 5 Inventory Feed Errors Costing 10% of VDP Traffic
Sponsored by Gas.net — powering dealership growth through intelligent data.
Alt text: “Gas.net connects franchise dealers with integrated analytics and marketing tools.”