Guide
What a restaurant website actually needs (and the PDF menu killing yours)
Diners visit your site to answer three questions in under thirty seconds. Most restaurant websites fail all three — starting with the menu buried in a PDF.
May 6, 2026 · 6 min read
A hungry visitor lands on your site with three questions: what's on the menu, are you open, and how do I order or book. If any answer takes more than a scroll and a tap on a phone, a real share of them leave for the next tab. Restaurant sites lose more customers to friction than to competitors.
The single most common failure is the PDF menu. It's slow to load, unreadable without pinch-zooming, invisible to Google — which means your dishes can never rank for 'best lamb plov near me' — and unreadable to the AI assistants diners increasingly ask for recommendations. Your menu belongs on the page as real text, with prices.
The non-negotiables
Menu as HTML with current prices. Hours, address, and a click-to-call number visible without scrolling. An 'Order Online' button in the header that goes to your own ordering page — not a link that hands the customer to a 25%-commission app. Real photos of your food and room, because stock photography reads as fake within a second.
Then the layer most restaurants skip: schema markup that tells search engines your cuisine, price range, hours, and menu items. It's invisible to visitors and decisive for whether you appear in map results and AI answers.
Speed is a menu item
Restaurant sites carry heavy images, so speed discipline matters more than in most industries. Under three seconds on a phone connection is the bar — every second past it costs a measurable slice of visitors, and hungry visitors are the least patient on the internet.
Elevaro builds restaurant sites with the HTML menu, integrated direct ordering, schema markup, and ongoing management — so the menu on your site is never three prices out of date.