A restaurant’s site is light, and one of the first shared plans is enough. A restaurant needs three things: a menu that reads well on a phone, photos that do not take long to open, and a way to book or talk to the house. The plan is the easy part. What makes the difference is the site opening quickly on a phone, at the hour people choose where to go.
What weighs, and what does not
| Part of the site |
What to do |
| The menu |
Write it as text on the page, and offer the PDF as a download on top. A multi-megabyte PDF that opens on a phone is the commonest cause of complaints. |
| Photos of the dishes |
They are the weight of the site. Resize and use WebP. See image optimisation and WebP. |
| Bookings |
A simple form is enough for many. A proper booking system can be a plugin or an outside service embedded in the page. Test properly the e-mail that notifies the house. See why your e-mail is not sending or receiving. |
| Contact by WhatsApp |
A link or a button does it. See putting WhatsApp on your site. |
| Showing up on Google |
Counts for more than the plan. See being found on Google. |
How to choose, step by step
| 1 |
Start with the entry plan. A restaurant with a brochure site and a form has few simultaneous requests.
|
|
| 2 |
Test on a phone, on mobile data and not only on Wi-Fi. That is how most people open the site. If the menu is slow, the problem is the file, not the plan. See Core Web Vitals in plain words.
|
|
| 3 |
Put the address, opening hours and phone number in text, not in an image. It is what people look for first and what Google reads.
|
|
| 4 |
Review the plan only if the site starts doing more: delivery orders, payments, several restaurants. On that day the restaurant has become a shop: which hosting plan for an online shop.
|
|
Give the customer the shortest path
Someone looking for a restaurant on a phone wants one of three things: to see the menu, to know where it is, or to book. Put a call button and a WhatsApp button at the top of the page, and the map straight after. The fewer taps to a booking, the more bookings. The rest of the site is for people who want to know more.
|
Watch the weekend and festive-date peaks. Visits do not come spread across the day: they bunch up at the hours when people decide where to eat. A light site with caching copes; a heavy one slows down exactly then.
|
|
A restaurant’s details change: hours, the dish of the day, holidays. Pick a tool in which the team can edit the text without asking anyone.
|
|
Want to put the restaurant online and unsure where to start? Tell us what you need and we will name the simplest plan.
Open a support ticket
|
RECOMMENDED PRODUCT Web hosting with cPanel Domain and SSL included, daily backups and the panel you already know. from 5.940,00 Kz/mo (3-year plan, with coupon) See plans |
Português
English
