Most of your traffic is on a phone. Is your site ready?

Pull up your analytics right now. Look at the device breakdown for the last 90 days. If you run a rafting company, a fishing guide service, or any outdoor recreation business, somewhere around 65% to 75% of your visitors are on a phone.

Now open your own site on that phone and try to book a trip.

Whatever you just felt, your customers feel it every single day. Most of them don’t stick around to figure it out. They hit back and book with someone whose site works on a small screen.

The gap between mobile traffic and mobile bookings

About 70% of online travel traffic now comes from mobile devices. Desktop still accounts for roughly 62% of actual bookings.

Most sites make it unreasonably hard to complete a booking on a 6-inch screen. Travel conversion rates are 3.9% on desktop and 1.4% on mobile. If you get 4,000 mobile visitors a month during peak season and your conversion rate sits two percentage points below what a decent mobile experience would deliver, that is 80 missed bookings. At $150 per person, $12,000 a month walks out the door while your site technically “works.”

Mobile checkout takes 40% longer than desktop on average. Form abandonment runs twice as high. The travel industry sees cart abandonment rates between 79% and 85%, and the bulk of that is friction on small screens.

Your customers are booking from the passenger seat

Your customers are not at a desk. They are in a hotel lobby the night before, or passing through your town on a road trip, or standing at a trailhead with two bars of signal trying to book something for tomorrow morning.

Your site has to load fast on bad connections. A 4MB hero image of a raft on the Snake River is fine on Wi-Fi with a laptop open. On a spotty cell connection in a mountain valley, it kills the page. Rural connectivity is still terrible in the places where outdoor recreation actually happens. Over 1,300 US counties have internet speeds below the FCC broadband threshold. Hills, trees, and valleys scatter cell signals before they reach your customer’s phone. Cell towers in rural recreation areas are spread far apart, and foliage makes it worse.

This is the part most web designers miss. They test on fast office Wi-Fi and call it good. Your customers are loading your site on 3G in a canyon. Build for that.

If your site does not work for that person, someone else’s will.

What google measures on your mobile site

Google has ranked sites based on their mobile version since 2023. A beautiful desktop experience with a slow mobile counterpart means lower rankings across the board.

Google tracks three metrics called Core Web Vitals. They matter because they directly affect where you show up in search results.

LCP (Largest Contentful Paint) measures how fast the main content on your page becomes visible. Google wants that under 2.5 seconds. That hero photo of your guided fly fishing trip on the Madison River needs to appear within that window or Google marks the whole page as poor.

INP (Interaction to Next Paint) is responsiveness. You tap “Check Availability” and nothing happens for half a second. Google notices. The threshold is 200 milliseconds, and around 43% of websites still fail it. Sites loaded with booking widgets and third-party scripts tend to be the worst offenders.

CLS (Cumulative Layout Shift) measures whether elements jump around while loading. You have seen this on your own phone: you start reading a trip description, a booking widget loads late, and everything shoves down the page. Google’s threshold is 0.1, and most sites with embedded widgets blow past it.

A slow mobile site means fewer people find you in the first place, which compounds the cost of slow page speed all season long.

The fixes that actually matter

You do not need to rebuild your site. Most of this is fixable in a weekend.

Start with images. This is the fastest win for most outdoor sites. Your photographer delivered 4MB files, but on a phone screen, a 200KB WebP version looks identical. Run every image through ShortPixel or Squoosh. Target under 200KB each. On image-heavy sites, this alone can cut load time in half.

Then test your booking flow on your own phone. Go through every step. If the date picker needs precision tapping on tiny calendar squares, if a dropdown has 30 options you have to scroll through, if the form resets when you accidentally swipe back: those are the moments your customers bail. FareHarbor’s Lightframe embed keeps the entire checkout on your site without a redirect. Operators who switched to it saw a 22.6% conversion lift. Peek and Checkfront have similar widgets. The catch is that these need to be configured for mobile, not just installed with default settings.

Keep the booking flow under 60 seconds. Name, date, group size, payment. That is all you need up front. Everything else can go in a confirmation email.

Readability matters more than people think. Set your body text to at least 16px and add spacing between paragraphs. Your customers are reading on a screen smaller than a postcard. Dense text in small font means they leave.

Check your tap targets while you are in the CSS. They need to be at least 48 pixels tall with clear spacing between them. If your “Book Now” button sits right next to a “Learn More” link and both are 30 pixels tall, people tap the wrong one constantly. Every wrong tap costs you.

Make your phone number a tappable link. Someone at a put-in spot on the Nantahala who wants to book a last-minute trip should be able to call you with one tap. A phone number baked into an image or styled as plain text forces them to memorize it and switch apps. That call does not happen.

Run the test yourself

Go to pagespeed.web.dev. Enter your homepage URL, then your most popular trip page. The tool shows you exactly where your mobile experience falls apart, scored and prioritized by impact.

Fix the red items first. Most of the issues it flags (image sizes, tap target spacing, render-blocking scripts) are things your web developer or platform provider can handle in a few hours.

If you want a broader look at what your website should be doing as a booking engine rather than a digital brochure, start there. Then check the five pages every outdoor website needs and make sure each one passes the phone test.

One more thing worth doing: pull up your trip pages on your phone and look at them like a stranger would. Not as the owner who knows every detail of the trip already, but as someone who found you through a search result 30 seconds ago. Can they tell what the trip is, how much it costs, and how to book within one scroll? If not, the page is working against you regardless of how fast it loads. The off-season is when smart operators overhaul their sites so these problems are gone before the phones start ringing.

Do this before peak season. By the time someone searches “guided rafting trips near me” from a campsite in June, your site either works on their phone or it does not. There is no fixing it mid-season when you are on the river every day.