Campsites: your visitors are on a bad signal

Campsites and glamping sites have an unusual audience problem: a large share of the people looking at your site are already near it, in the countryside, on a phone with poor reception, and often at the exact moment they need an answer.

That reverses the usual advice. Optimising for a fast connection is pointless when your typical visitor has a slow one, and chasing a seconds figure is frustrating when the network is doing most of the deciding.

So the approach here is a payload budget, measured in kilobytes, applied to the two heaviest things a campsite site owns: photography and the pitch map.

Every campsite wants a site plan showing pitches, hook-ups and facilities, and there are three ways to do it. A scanned image is often two megabytes for something illegible on a phone. An interactive map plugin adds a script bundle and tile requests. A properly drawn vector plan is usually well under a hundred kilobytes and stays sharp at any zoom.

The third option is almost always right and almost never chosen. If you are stuck with an image, export it at a sensible width, let built-in WebP conversion run, and put it behind a tap rather than loading it on arrival. Then re-read the transfer total and confirm the budget is back under control.

Bookings cluster around school holidays, bank holidays and the first warm weekend of the year. Check field data in PageSpeed Insights just after one of those, because the rolling 28-day window at the 75th percentile still contains it, and that is when your visitors were most likely to be on a stretched network.

Between seasons, use a staging clone to try the changes: a vector site plan, a lighter gallery, a deferred availability check. Measure on the clone, promote what worked, and keep the transfer totals written down so next season's comparison takes a minute rather than an afternoon.