What does a restaurant website actually need?

Four things, fast: the menu, opening hours, location with a map link, and a way to book or call. Everything else is secondary. The most common mistake is a beautiful slow homepage that hides the menu behind a download or a heavy widget. Put the essentials one tap away.

Should the menu be a PDF?

Ideally not. A PDF menu is slow to open on a phone, awkward to read, and bad for search. A menu built as a real web page loads instantly, reads well on mobile, and helps you show up in searches for the dishes you serve. We can still keep a printable version alongside it.

Why is my restaurant website slow on mobile?

Usually big food photos that were never resized, a heavy theme, and booking or social widgets loading before the content. Food photography is worth keeping, but it needs to be sized properly and load after the essentials, not before them.

Can customers book a table after the rebuild?

Yes. We keep your reservation system or link and put it where a hungry thumb expects it. If you take bookings by phone, the number becomes one tap on mobile. The booking step should never be the slow part of the page.

Websites for restaurants

Hungry people are on their phones. Your website is still loading.

The phone is the whole game

Most people open a restaurant website on a phone, often minutes before deciding where to eat. They are not browsing for fun. They want to know what you serve, whether you are open, where you are, and how to book. The site that answers fastest usually wins the table.

A slow, image-heavy homepage that hides the menu is not a style choice. It is a leak in your bookings.

What we keep

We keep your menu and prices, your best food photography, your hours and location, your reservation link, and the personality that makes the place yours. Restaurants usually have great raw ingredients for a site. The problem is how they are plated.

What we replace

We replace PDF menus with a real web menu that loads instantly and helps you show up in search. We resize heavy food photos so they stay beautiful without stalling the page. We strip the widgets that load before your content and rebuild the whole thing mobile-first, so the essentials appear at once.

Proof it works

The Orfanus rebuild took a heavy site from 11 MB and 131 requests to roughly 0.2 MB and 11 requests, with performance climbing from 62 to 100. A restaurant site carrying lots of food photography is exactly the kind of page that gets dramatically faster when the images are handled properly and the content loads first.

How it works

Send your URL. We send two clickable previews, you choose one, and we ship it one to one at a fixed price in about 10 to 14 days. No moodboard workshops, no weekly calls. The menu loads before the visitor gets hungry enough to leave.

Send your restaurant's URL

Two previews, a fixed price, and a site that serves the menu before the visitor gives up and orders elsewhere.