Research Series / No. 04 / Web Performance

Page Speed and
restaurant booking rates.

A hungry person on their phone at 6pm has no patience and three other tabs open. If your site makes them wait, they do not wait. They book the place that loaded.

Published / by Loki Kumar

We pulled together what we could see across about forty hospitality venues we have worked with or looked at closely, cafes, restaurants and a couple of wine bars, and lined their website load time up against how their bookings behaved. We went in expecting speed to matter. We did not quite expect how cleanly the line would fall. The faster sites were not just nicer to use. They were turning more of the same traffic into actual reservations, and the slow ones were leaking diners they never knew they had.

I want to be honest about what this is. It is not a controlled study with a clean sample. It is a field read across a real, messy set of venues, and the numbers are directional. But the pattern was consistent enough, and matches what is well known about how people behave on slow pages, that I would bet money on it for almost any venue.

53%of mobile visitors leave a page that takes over three seconds to load
~7pmthe nightly spike when most booking traffic hits, almost all of it on phones
1 taphow far the booking should ever be from the moment someone decides
01

The line we kept seeing

When we grouped the venues by how fast their site loaded on a normal phone, the relationship with booking behaviour was hard to miss. The quick sites converted browsing into reservations at a noticeably higher rate, and the gap got worse the slower things got. Below a certain speed it was not a gentle decline, it was a drop, because that is the point where impatient people simply give up and go elsewhere.

Mobile load timeWhat it feels likeWhat we saw happen to bookings
Under 2 secInstant. The diner barely notices the siteStrongest conversion, bookings flow without friction
2 to 3 secFine, a small wait nobody resentsHealthy, only a slight drop-off
3 to 5 sec"Come on", thumb starts drifting to the back buttonNoticeable leak, a real share leave before booking
Over 5 secFeels broken, like the place might be closedHeavy loss, many never reach the booking at all

The cruel part is that the venue never sees any of this. The diner who bounced off a slow page does not send a complaint. They just eat somewhere else, and the owner assumes it was a quiet night. The lost bookings are completely invisible from the inside, which is exactly why slow sites survive for years in businesses that would never tolerate a slow kitchen.

A slow website is a quietly closed door. The diner who bounces does not complain, they just book the place that loaded. Nunik Co. Research Series, No. 04
02

Why hospitality sites are slow

Hospitality has a particular weakness here, and it is almost always the same culprit. The food looks incredible, so the site is stuffed with enormous, beautiful, completely uncompressed photos. A gorgeous hero image that weighs as much as the rest of the page put together. A full-screen background video that autoplays and chokes the load. The very thing meant to make the place look appetising is the thing making the door stick.

The other usual suspects are a pile of plugins and tracking scripts nobody remembers adding, a booking widget that drags in a slow third-party script, and a theme that was never built with phones in mind even though phones are where nearly all the booking traffic lives. None of this is exotic. It is the ordinary accumulation of a site that grew over a few years and was never once looked at through the eyes of a hungry stranger on a train.

The thing the whole site is actually for

The booking is the page. Everything else is wallpaper.

It is easy to forget, but a restaurant website has exactly one job. Get a hungry person to a confirmed booking with as little friction as possible. The menu, the photos, the story, all of it is in service of that one tap. If the booking button is hard to find, slow to load, or buried two clicks deep, the prettiest site in town is still failing at the only thing that pays the bills.

03

What actually moves the number

The good news is that fixing this is not a rebuild, most of the time. The wins are unglamorous and they are fast, which is the kind of work I like. In rough order of return:

  • Compress the images. The single biggest lever, almost always. Properly sized, modern-format images can cut load time dramatically without anyone seeing a difference in quality. This one fix often does most of the job.
  • Kill the autoplay video. A background video is the heaviest thing on most hospitality sites and adds almost nothing. Lose it, or replace it with a single sharp photo.
  • Put the booking one tap away. A clear, fast, always-visible "Book a table" that does not depend on a sluggish third-party script to appear. The decision is fragile, do not make them hunt.
  • Strip the dead weight. Remove the plugins and scripts nobody uses. Every one of them is a small tax on every single visit, paid forever.
  • Test on a real phone on mobile data. Not your fast office wifi. The way a diner actually experiences it on the train at 6:50pm is the only test that counts.

The mindset shift

Speed is hospitality, not just tech

A venue would never make a guest stand at the door for ten seconds while someone decides whether to acknowledge them. Yet a slow website does exactly that to every single visitor, all night, every night. Treat load time the way you treat a warm welcome. The site is the front door now, and most of your guests meet it before they ever meet you.

If you only do four things this year

Where to start.

  • Test your own site on a phone, on mobile data. Time it. If it takes more than three seconds to be usable, you are losing bookings tonight and every night.
  • Compress the images first. It is the biggest, cheapest win. Most hospitality sites are slow for this one reason alone.
  • Make the booking button impossible to miss. One tap, always visible, fast to load. The whole site exists to get someone there.
  • Cut the autoplay video and dead plugins. Beautiful and heavy is still heavy. Lean and fast wins the 7pm rush.

About this report. The figures here combine Nunik Co.'s own observations across roughly forty Australian hospitality venues we have worked with or reviewed through late 2025 and the first half of 2026, alongside well-established findings on mobile load time and bounce behaviour. The booking-rate patterns are directional rather than a controlled study, and we have framed them that way on purpose. If you want us to time your site the way a real diner experiences it and show you where the bookings are leaking, talk to us.

Book directly

Pick a time. Talk to us.

Fifteen minutes. We scope the right first move. No pitch deck.