Tithi MondalBlog

Article5 min readUpdated

Restaurant Website Design: Menu, Booking and Photos

Restaurant website design for Indian cafes and eateries: a clear digital menu, QR menu, table booking flow and food photo layout that sells.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Restaurant Website Design: Menu, Booking and Photos: cover illustration

The diner is standing outside your door

Suppose a cafe in a tier-2 town is full on Saturday evening. A family of four stands outside. They open Google Maps on a phone, tap the cafe, and tap "Website". The site takes 8 seconds to load a large banner. Then it shows a PDF menu in tiny print. They give up and walk to the next place.

This is the real test of restaurant website design. Visitors are hungry, on a phone and on a weak network. They want the menu, the price, the timing and a way to reach you. Everything else is decoration.

What a restaurant site must do

Before you choose colours, decide the one main action. Most places fall into one of three groups.

  • Dine in cafe: the main action is "Book a table" or "Get directions".
  • Takeaway or delivery kitchen: the main action is "Order now".
  • Restaurant with events and catering: the main action is an enquiry for a party or a bulk order.

You can serve more than one action, but only one gets the biggest button. I designed MyFoodBox, a restaurant ordering product, and the first thing I fixed in every flow was this question: what does the visitor do first? My article on food delivery app UI UX design goes deeper on ordering apps.

The six pages and screens that matter

1. Home page

Show the restaurant name, cuisine in plain words, area, opening hours, and two buttons: "View menu" and "Book a table" or "Order". Add one strong photo of a real dish or the real room. Show whether you are open right now. A line like "Open today until 11 pm" saves a phone call.

2. Digital menu

The digital menu design is the heart of the site. Use plain text with categories that stick to the top while scrolling: Starters, Mains, Rice, Breads, Desserts, Drinks. Each item has a name, a short description of 1 line, the price in rupees and a veg or non veg mark. Mark the spicy and bestseller items only if the kitchen agrees. Never use a PDF as the only menu. A PDF is slow, hard to read on a small screen and invisible to search engines.

3. QR menu

A QR menu is a printed code on the table that opens the menu page in the phone browser. Use the same menu page as the website, so you update prices in one place. Make sure the page opens without login and without an app download. Keep text large, because people read it in dim light. Add a "Call the waiter" button only if the staff will really respond.

Show food in a grid of 6 to 12 photos, each with a dish name. Photograph in daylight near a window, from slightly above, on a clean plate. Use real photos of your own food. Photos that look better than the real plate create unhappy guests. Compress every image so the page stays light. See designing for low end phones and slow networks.

5. Table booking

The next section covers this flow.

6. Find us

Put the address, a map link, parking notes, phone number and WhatsApp button together. Add a landmark in words. Include opening hours for each day, including festival days when the timing changes.

The table booking flow, step by step

Keep it short. A diner should finish in under a minute.

  1. Pick the date. Show today and the next 6 days as large buttons.
  2. Pick the time. Show lunch and dinner slots. Hide slots that are full.
  3. Pick the number of guests. Use plus and minus buttons, from 1 to 8. For larger groups, show "Group of 9 or more? Send an enquiry".
  4. Add name and mobile number. Add an optional note for birthdays or a high chair.
  5. Confirm. Show the booking summary, then send it by SMS and WhatsApp. Include a cancel link.

Do not ask for an email address. Do not force a login. If the restaurant holds tables only for 15 minutes, say so on the confirmation screen.

Ordering and payment

If you also take orders, keep the order flow separate from the menu browsing, but let the same menu feed both. Add to cart should be one tap. Show the running total in a bar fixed at the bottom of the screen. Offer UPI first, then cash on delivery if you allow it. My notes on UPI payment UX explain why a clear payment screen reduces failed orders.

Keep the menu short enough to scan. Twenty clear items sell better than eighty items in small print. Group items by how people order: a thali, a combo, a family pack. Put the most popular items first, because most guests choose from the first screen.

Be honest about delivery time. If the kitchen needs 30 minutes at the dinner rush, show that. A wrong promise creates more complaints than a longer, true one.

How a cafe site differs from a large restaurant site

A cafe site is often one long page: photos, a short menu, the story, timings, a map. The cafe mood matters. Show the seating, the coffee, the music and the quiet corners. Customers choose a cafe for the feeling, so the photographs of the space do more work than on a restaurant site.

A larger restaurant needs more structure: separate menus for lunch, dinner and buffet, a private dining page, and a catering enquiry form. Keep the words of the menu in the language your guests use. A Bengali sweet shop in Kolkata may want item names in Bengali and English together. Check that the Bengali font looks clear on a cheap phone.

Mistakes on restaurant websites

MistakeWhat to do instead
Menu only as a PDFBuild a real web page menu with text and prices
Prices missingShow every price in rupees, including taxes if charged
Huge uncompressed photosCompress images and load them lazily
Music that plays automaticallyRemove it. Visitors are often in public
Opening hours only inside an imageWrite the hours as text
Booking form with 8 fieldsAsk for date, time, guests, name and mobile number
Old festival offers still showingAdd a date to every offer and remove it after
Stock photos of food you do not serveUse photos of your own dishes

One more point: update the menu the same day prices change. A wrong price on the website causes arguments at the table.

If you want a menu, booking flow and photo layout designed for your restaurant, see how I approach website design or write to me on the contact section.

Frequently asked questions

Do I need a website if I already have a Zomato or Instagram page?

+

Yes, it helps. A website is the one place you control: menu, prices, booking and your story. Delivery platforms and social pages can link to it.

How do I make a QR menu for my cafe?

+

First build a mobile menu page with text and prices. Then create a QR code that points to that page and print it on table cards. Update the page and the QR code keeps working.

What is the best way to photograph food for a website?

+

Use daylight near a window, shoot from slightly above, and keep the plate clean. Use your real dishes and compress the files before uploading.

Should my restaurant website take online orders?

+

Only if the kitchen can handle them. Start with the menu and table booking, then add ordering when you can promise a true delivery or pickup time.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.