Mobile Websites for Powersports Dealers: What Google Measures and What Shoppers Tap

When this article first ran in 2019, it summarized a Google study about people reaching for their phones in idle moments: the waiting room, the train, the lunch line. That page has since been retired, and the point it made is now simply how the web works. A shopper looking at a side-by-side on a lunch break is looking at your mobile site, and so is Google.

This rewrite covers the site side: what your dealership website has to do on a phone, the numbers Google publishes, and how to test it yourself. If you want the shopper side, how riders actually use their phones from first idea to delivery, read the companion piece on how powersports shoppers use their phones.

Why the phone version is the version that counts

Google states it plainly in its Search Central documentation: "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." This is mobile-first indexing.

For a dealer, that has three practical consequences:

1. What the phone shows is what Google ranks. If your mobile vehicle detail page (VDP) drops the spec table, the description or the price disclaimer to save space, Google judges the unit on the thinner page.
2. Titles, descriptions, structured data and image alt text must match. Google asks that "the title element and the meta description are equivalent across both versions," that both have "the same structured data," and that the mobile site has "the same alt text for images as the desktop site."
3. A separate "m-dot" mobile site is a liability. Older dealer platforms built a stripped-down second site for phones. If yours still does, it is the version being indexed.

Mobile parity: what your phone VDP may be hiding from Google

Most dealer website checklists stop at "make it responsive." The quieter problem is a responsive site that looks fine on a phone but loads less there.

Google's guidance is specific: "Google won't load content that requires user interactions (for example, swiping, clicking, or typing) to load." It adds a direct rule: "Don't lazy-load primary content upon user interaction."

On a powersports VDP, that catches four common patterns:

• Photo galleries that fetch images only when the shopper swipes. Google sees the first photo and nothing else. Load the gallery's images in the page and let the browser defer the off-screen ones, rather than waiting for a swipe to request them.
• Specs, features and descriptions that load only when a tab is tapped. Collapsed sections are fine when the text is already in the page. They are a problem when tapping is what fetches the text.
• "Show more inventory" buttons with no crawlable pages behind them. If the only way to reach unit 25 is to tap "Load more" three times, give the list real paginated URLs as well.
• Different data on desktop and mobile. OEM feed text, price disclaimers and vehicle structured data sometimes appear only on the desktop template.

The quickest check: open a VDP on your phone, then on a desktop, and compare what is in the page, not what is visible. If your web provider cannot show you that both templates carry the same content and structured data, ask them to.

Core Web Vitals on a phone: the three numbers

Google's web.dev team publishes three Core Web Vitals and a "good" threshold for each. They are measured at "the 75th percentile of page loads, segmented across mobile and desktop devices," which means a desktop pass tells you nothing about phones. Mobile is scored on its own.

A page passes when it meets all three at the 75th percentile. Many dealer sites do not. In February 2025, Overfuel, a dealer website vendor, reported that only 15.7% (363) of the 2,315 powersports websites it checked against Google's real-user data passed on both mobile and desktop. Treat that as one vendor's study, not an industry census.

The usual causes on a dealer site: full-size unit photos sent to a phone, a hero slider of OEM banners, stacked chat and tracking scripts, and images without set dimensions. Our wider dealer website best-practice checklist covers speed on every page type; on mobile, start with the homepage and your VDP template, because that is where most phone visits land.

Tap targets: built for thumbs, sometimes in gloves

Shoppers tap with thumbs, often outdoors. Small, crowded buttons cost you taps.

• Size. Google's web.dev guidance says "a minimum recommended touch target size is around 48 device independent pixels," which "corresponds to around 9mm, which is about the size of a person's finger pad area."
• Spacing. The same guidance says targets "should also be spaced about 8 pixels apart, horizontally and vertically."
• Accessibility floor. WCAG 2.2 success criterion 2.5.8, Target Size (Minimum), is Level AA and asks for targets of "at least 24 by 24 CSS pixels," with exceptions such as enough spacing or an equivalent control elsewhere on the page.

Treat 24 pixels as the floor and 48 as the goal for anything a shopper uses often: call, text, directions, filters, photo arrows and form buttons. If accessibility is on your list, our guide to an ADA compliant powersports dealer website covers the rest of WCAG.

Fast VDP photo galleries

Photos are why shoppers open a VDP, and the heaviest thing on it. A gallery can be complete and fast:

1. Serve phone-sized images. A phone does not need a 4,000-pixel original. Use responsive image sizes so each device gets a file that fits its screen.
2. Set width and height on every image. The browser reserves the space, so the page does not jump when photos arrive. That protects CLS.
3. Load the first photo right away and defer the rest. Use the browser's native lazy loading for off-screen images, not a script that waits for a swipe.
4. Show the count. "1 of 32" tells the shopper there is more to see, and pinch-to-zoom lets them check tires, plastics and hour meters.
5. Put the actual unit first. A stock OEM image in slot one wastes the most-viewed position. Our guide to powersports inventory photos has a shot list by vehicle type.

Click-to-call, click-to-text and short forms

On a phone, the lead form competes with the phone itself. Give shoppers both:

• A sticky action bar on VDPs with Call, Text and Directions. Phone links should dial on one tap, and a text link should open the messaging app with your store number filled in.
• Short forms. Name, mobile number or email, and a message box are enough for a unit question. The unit should be filled in automatically from the page.
• The right keyboard. Phone fields should bring up the number pad, and email fields the email keyboard. Use autocomplete so a phone can fill name and number in one tap.
• A clear promise of what happens next, such as "We reply by text during open hours."

If you offer text, the consent rules matter. Our guide to texting powersports customers the right way covers consent, registration and opt-outs. This is general information, not legal advice.

The mobile audit: a scorecard you can run

Run this on a real phone, on cellular data, not office Wi-Fi.

How to test on real phones, step by step

1. Borrow a mid-range Android phone. PageSpeed Insights' lab test simulates "a mid-tier device (Moto G4)" for a reason: most shoppers do not own the newest flagship.
2. Turn Wi-Fi off. Test on cellular, ideally from your lot or service drive.
3. Run five shopper jobs and time each: find a used side-by-side under a set price, open its VDP and view every photo, find the price and any fees note, text the store about it, and get directions.
4. Check field data. PageSpeed Insights shows real Chrome users' results for "the previous 28-day collection period." If a page lacks enough data, it falls back to the whole site, so test your busiest templates.
5. Compare phone and desktop VDPs for missing content, using the parity checks above.
6. Submit a real test lead and follow it into the CRM: the unit, the source and the shopper's preferred channel should all be there.
7. Fix in order of traffic. VDPs and inventory lists first, then the homepage, then everything else. Re-test a month later, once a new 28-day window has collected.

For the homepage specifically, our sibling guide on nailing your powersports dealership homepage covers what belongs above the fold.

You can also see the same certified dealership websites on our sister site, PSXDigital's certified dealership websites page.

How PSX Ascend builds dealer websites for phones

PSX Ascend's certified powersports websites are designed to adapt across phones, tablets and desktops while keeping inventory, forms, conversion paths and essential customer actions accessible. The design aim is to keep filters, forms, calls and vehicle actions comfortable to use on smaller screens, and to keep the information and conversion paths that matter rather than hiding them on mobile.

The site runs inside the same connected platform as the AI-powered powersports CRM, so a lead submitted from a phone arrives with the vehicle, the source and the requested action attached, and the team can answer by phone, text or email. On the inventory side, AI inventory management gives staff a guided mobile workflow to photograph units and complete details from a smart device, which keeps VDP photos current.

Sources

• Google Search Central, Mobile site and mobile-first indexing best practices, last updated December 10, 2025.
• web.dev, Web Vitals, last updated October 31, 2024.
• web.dev, Accessible tap targets, last updated March 31, 2020.
• W3C Web Accessibility Initiative, Understanding Success Criterion 2.5.8: Target Size (Minimum), WCAG 2.2.
• Google for Developers, About PageSpeed Insights, last updated October 21, 2024.
• Overfuel press release via Business Wire, New Study from Overfuel Exposes Powersports Industry's Online Performance Gap, February 17, 2025 (vendor study of 2,315 powersports websites using Chrome UX Report data).