Book yourself on your own phone. Time it.

It's 7pm. Someone decides they want a table for Saturday. They're on the sofa, phone in one hand, and they type your name into Google.

What happens next is either a booking or a lost customer. You probably don't know which, because you've never done it yourself.

The test

Do this now, on your phone, with one hand. Don't cheat by using your desktop.

Search for your business by name. Find the booking option — not the phone number, the actual online booking. Start filling it in. Pick a date, a time, a party size. Submit. Wait for the confirmation.

Time the whole thing from the Google result to the confirmation screen.

If it took under two minutes and you didn't have to pinch the screen to read anything, you're in decent shape. If you gave up, switched hands, or opened a new tab to find a phone number — that's what your customers are doing.

What usually breaks

The most common failure isn't a broken form. It's a form that works technically but defeats people in practice.

The date picker built for a mouse. Tiny arrows, a calendar that doesn't respond to a swipe, fields that open a keyboard when you need a date wheel. On a desktop it's fine. On a phone in a dark restaurant it's maddening.

Two-step verification before the booking. Create an account. Confirm your email. Then come back and finish. Most people don't come back.

A phone number where a form should be. "Call us to reserve" is not a booking system. It's a barrier. Calls don't get answered at 7pm on a Tuesday, and the customer who wanted Saturday has already moved on.

A form that resets on submit. You fill everything in, hit book, and the page reloads empty with no message. Did it work? Most people assume it didn't, and either try again — creating a duplicate — or give up entirely.

No confirmation. You get a "thank you" on screen but no email, no calendar invite, nothing you can screenshot. Three days later you're not sure whether you're actually booked.

What a working booking flow looks like

Straight to the form — no account required for a first booking. Date, time and party size in three taps, each field sized for a thumb. A submit button that doesn't require scrolling to reach. An immediate confirmation on screen and in email within thirty seconds, with the booking details, a cancellation link, and your address.

The whole thing under ninety seconds on a 4G connection.

That's the bar. It's not complicated. Most sites don't clear it because the booking widget was added after launch, nobody tested it on a real phone, and the business owner only ever sees it from a desktop.

Why this matters more than the homepage

You can have a beautiful homepage and lose every evening customer to the place down the road that just has a working OpenTable embed.

The homepage is marketing. The booking form is the transaction. If the transaction fails, the marketing was wasted.

A customer who can't book doesn't complain. They don't email you. They just book somewhere else and you never find out. Your analytics show traffic, your phone stays quiet, and the gap between the two looks like a mystery.

It isn't. It's the form.

What to do if the test fails

Write down the exact step where it broke. Not "the booking process is bad" — the specific moment: the date picker, the required account, the missing confirmation email. That's what goes in the brief when you get it fixed.

If you're on a template widget you can't change, the fix might be replacing it with something built around how your customers actually book — phone in hand, low patience, one shot at it.

If you'd like us to look at it, the 30-minute intro call is the right place to start. Bring the broken step and we'll tell you honestly what it would take to fix.