Page speed and bookings: what slow loading actually costs you

A family searches “kayak tours near me” from their phone at a campground. They tap your site. The page hangs. Three seconds pass and the hero image is still blank. They hit back and book with the outfitter whose site loaded first.

That happens thousands of times a day. The business that lost the booking never sees it in their analytics. No error log. No angry email. Just a visitor who vanished before the page finished rendering.

We wrote about page speed and bookings a few weeks ago. Since then, Google raised the stakes. The March 2026 core update increased the ranking weight of Core Web Vitals, and a metric called INP now measures how fast your site responds when someone taps a button or interacts with a booking widget. If your site was borderline slow last year, it’s costing you more now.

The numbers are worse than you think

The conversion data has only gotten sharper. Pages that load in one second convert at 2.5 times the rate of pages that load in five seconds. Sub-second sites see conversion rates around 9.6%. Five-second sites sit at 3.3%.

For travel sites, improving load time by just a tenth of a second increases conversions by 10.1%. That’s not a rounding error. On a trip page that gets 400 visitors a month with a $200 average booking value, a tenth of a second is the difference between roughly $2,400 and $2,640 in monthly revenue. From one page.

Bounce rates tell the same story. A two-second delay increases the probability of bouncing by 103%. More than half of mobile users leave entirely if a page takes over three seconds. Your customers are checking your site from a parking lot or a hotel lobby on cellular data. Three seconds is generous for that context.

What changed in 2026

Two things.

Google’s March 2026 core update gave more ranking weight to Core Web Vitals. Previously, these metrics were a tiebreaker. Two rafting companies with similar content and backlinks, the faster site won. Now the effect is bigger. Ahrefs reported that 55% of tracked domains saw ranking movement of five or more positions within the first week of rollout. Sites with a Largest Contentful Paint above three seconds lost 23% more traffic than faster competitors.

Then there’s INP. It replaced First Input Delay as a Core Web Vital in March 2024, and it’s now fully baked into how Google evaluates your site. INP measures the delay between a user interaction, like tapping your “Book Now” button, and the browser actually responding. Good is under 200 milliseconds. Only 48% of mobile pages pass all three Core Web Vitals right now, and heavy third-party scripts are a big part of why.

Why outdoor recreation sites fail these metrics

Outfitter and guide websites are built to look like the experiences they sell. Big wide-angle photos of rivers and mountains, embedded booking widgets, maybe a video header. All of that looks great. It also takes forever to load.

The typical site we audit has uncompressed images weighing 4-8 MB each, three or four on a single page. A homepage totaling 20 MB when it should be under 2 MB. The person on a cellular connection near your put-in location doesn’t have the bandwidth for that.

Booking widgets are the other culprit, and this is where INP shows up. Platforms like FareHarbor, Peek, and Checkfront load JavaScript that runs on the browser’s main thread. When that script is executing and a visitor taps something, the browser can’t respond until the script finishes. The page just feels sluggish, and the visitor can’t tell you why.

Now add a chat plugin, a Google Maps embed, a Facebook pixel, an analytics tag, and a review widget. That’s fifteen external scripts competing for the same main thread. They all add latency, they all drag your INP score down, and after the March 2026 update, Google cares about that more than it used to.

How to check where you stand

Run your homepage and your most important trip page through Google PageSpeed Insights at pagespeed.web.dev. Look at mobile scores specifically. Below 50 needs work. Below 30 is actively costing you rankings and bookings.

Three numbers in the results matter most. LCP (Largest Contentful Paint) should be under 2.5 seconds. INP should be under 200 milliseconds. CLS (Cumulative Layout Shift) should be under 0.1. If any of those are red, start there.

GTmetrix still has the best waterfall chart for seeing exactly what’s loading and in what order. Sort by file size or load time. The offenders are usually obvious. Images first, then scripts.

Fixes that move the needle

You don’t need to rebuild your site. A few targeted changes can cut load times enough to pass Core Web Vitals and get those lost bookings back.

Start with images. This is almost always the biggest win. Run every photo through ShortPixel, TinyPNG, or Squoosh before uploading. Resize to the actual display size, because a photo shown at 1200 pixels wide doesn’t need to be uploaded at 4000 pixels. Convert to WebP. Image compression alone can cut page weight by 60-80%.

Turn on lazy loading for below-the-fold images so they only load when the visitor scrolls to them. Most website platforms have a toggle for this. If yours doesn’t, it’s a single HTML attribute.

Defer your third-party scripts. Your booking widget, chat tool, analytics, and social embeds don’t all need to load before the page is usable. Use async or defer attributes. Better yet, delay non-critical scripts until after the first user interaction. Moving your chat widget and social pixels to load on interaction instead of on page load can make a noticeable difference in your INP score.

Cut the scripts you aren’t using. Go through every plugin and external script on your site. If the chat widget rarely gets used, remove it. If the Facebook pixel isn’t driving measurable bookings, pull it. Every script you remove is one less thing blocking the main thread.

Upgrade from shared hosting if that’s your bottleneck. A $5/month plan puts you on a server with hundreds of other sites. When traffic spikes in May because people are booking summer trips, the server slows down during your busiest month. Managed hosting from SiteGround, Cloudways, or Flywheel costs $20-40/month. Some outfitters see load times drop by a full second just from switching hosts.

Set up a CDN. If your host is in Virginia but a visitor is in Oregon, a content delivery network means images load from a West Coast server instead of crossing the country. Cloudflare has a free tier. It takes about ten minutes to set up.

Speed is now a ranking factor with teeth

Google has used page speed as a ranking signal since 2018, and each major update since has turned the dial. The March 2026 core update turned it further than any before. For seasonal businesses competing on “rafting near me” or “guided fishing trips,” this matters because those searches happen on mobile, on spotty connections, from people who are ready to book right now.

Two outfitters in the same town with similar content? The one with faster Core Web Vitals gets the edge. After March 2026, that edge is wider. An SEO audit that skips a speed check is missing one of the most actionable ranking factors you can fix.

Your mobile experience is where most of your potential customers first meet your business. If it’s slow, they won’t wait.

When to do this work

You’re not going to overhaul your site speed in July when you’re running trips every day. This is off-season work. October or November, when you have time to test changes without risking peak traffic.

Block out an afternoon. Run the speed tests. Compress your images. Defer or remove the scripts you don’t need. Upgrade your hosting if that’s the bottleneck. By the time search volume picks up in spring, your site loads under two seconds and your booking flow is ready.

A tenth of a second matters. Not in some technical-debt-meeting way. In whether the person searching from their phone at a campground books with you or books with the outfitter whose site loaded first.