Journal · Brand
The one tweak that doubled LeCeylan's reservations
A two-line change in the homepage hero section roughly doubled weekly reservation submissions for LeCeylan, a Lankan-Lebanese restaurant in Beirut. Here's what we did and why we think it worked.
LeCeylan's homepage was, by every measure I'd usually use, fine. It loaded fast, looked beautiful, told the story of the food, and led visitors to a "Book a table" button. We launched it in October. By December, the owner — Jasem — sent me a polite message asking why "the website is pretty but the phone isn't ringing more."
He wasn't wrong. Direct site traffic was up 40% from the old site. Reservations were flat.
What we measured
I wired up a simple funnel: homepage view → "book a table" click → reservation form complete. The drop-off wasn't where I expected. Plenty of people clicked "Book a table." Almost nobody completed the form.
Looking at the form itself, the issue jumped out:
- The form had 8 fields.
- The first field was "Special dietary requirements."
- There was no available-time picker — you typed in a time, blind.
So we shortened the form. New version: 3 fields — name, party size, time slot (visual picker). Phone number requested only after the slot is held. Conversions improved, but only by maybe 15%. Not the doubling Jasem deserved.
The actual fix was upstream
The form change helped. But the real lift came from a tweak to the homepage, not the form. Specifically: the hero CTA.
The old hero said:
"A taste of Sri Lanka and Lebanon, in the heart of Beirut. Book a table."
Beautiful copy. I wrote it. Jasem loved it. It also moved nobody.
The new hero said:
"Tonight at 7:30, table for 4 — book in 15 seconds."
The CTA was now a live availability widget. The homepage didn't ask the visitor to imagine a future dinner. It offered them a specific table at a specific time tonight, with a 15-second commitment.
The data
Two weeks before the change, averaged: 14 weekly reservations from the website.
Two weeks after, averaged: 31 weekly reservations. Holding all other channels equal.
Direct walk-ins, Instagram DMs, and phone reservations stayed flat — so we don't think the lift was seasonal or driven by a non-web channel. It was the homepage.
Why I think this works
Three reasons, only one of which is design:
1. Specificity reduces decision cost.
"Book a table" is a future commitment. "Tonight at 7:30, table for 4" is a near-term concrete action. The visitor's brain doesn't have to do the work of imagining a future evening. The decision is already framed.
2. Live availability adds urgency without lying.
If 7:30 is shown as "1 left," that's true — and it works on the visitor's brain in a way that "Book now!" never could. We hate manufactured urgency. Real urgency is fine.
3. The visitor saw themselves, not the restaurant.
The old hero was about LeCeylan. The new hero was about the visitor's evening. Subject change. That's the whole game.
Jasem is, predictably, now asking us to do this for the catering page. We'll see if it works there. (My guess: it probably will, but with a different framing — caterers think in events, not evenings.) If it does, that'll be another post.