Vertical · Restaurants & Food Service
Hungry people decide in 90 seconds. Make every second count.
Diners choosing tonight's restaurant make the same three-step phone check: can I read the menu, do the photos look good, and are you open with a table available? Fail any in the first scroll and they choose the better website, not necessarily the better food. A hand-coded site follows that mobile decision process instead of builder defaults.
The 3 things people check before deciding where to eat
Restaurant sites discuss branding, photography and storytelling, but Tuesday-night diners make three mobile checks in roughly 90 seconds. Your page structure either speeds that decision or loses it. Here's where each step fails.
First: they check the menu
The menu is the most important page on a restaurant website and the most consistently mishandled one. Two bad approaches dominate: a PDF, and a menu loaded in from an outside service. Both look like solutions, but neither works on a phone in the hands of a hungry person.
PDF menus impose five steps: tap download, wait, open a reader, navigate a print landscape layout, pinch-zoom. On mid-range Android/LTE at 7pm, slow or poor rendering sends most diners to the next tab before choosing a dish.
BentoBox, SinglePlatform and Square's hosted menus look cleaner but add loading time and hide menu text from Google. Neither these embeds nor PDFs rank for "restaurants that serve [specific dish] near me." Google can read dishes built directly into your page.
Build sections (Starters, Mains, Sides, Drinks, Desserts), names, descriptions and prices directly into your page: under a second to load, no phone zooming, Google-readable. Update seasonal/86'd items and prices in a text file without logins, waiting or invoices.
Second: they look at the food photos
Food photos make an immediate emotional pitch: "Do I want this tonight?" Good photography answers in seconds. A six-second load with photos appearing piecemeal loses that decision.
Uncompressed photos commonly slow restaurant sites: print-sized professional shots or 4 to 6 megabyte phone images. Six homepage photos can total 30 megabytes before other content, taking 8 to 12 seconds on a decent phone connection. Most visitors leave by second four.
Three fixes: smaller modern formats without quality loss, images sized per device, and loading as visitors scroll. They bring that homepage under 8 megabytes on mobile, preserving food quality and loading before visitors leave. This influences restaurant choice more than redesign.
Separate galleries force diners reading about mushroom risotto to navigate elsewhere for its photo. Many decide from the weaker, text-only pitch. Put dish photos beside or within menu sections to turn interest into appetite without extra navigation.
Third: they confirm hours, location, and how to get a table
The person has seen the menu, liked the photos, and now needs to know three things: are you open right now, exactly where are you, and how do I get in? This is the moment where a lot of restaurant sites lose customers they already had because the information is either wrong, buried, or both.
Hours go stale: early kitchen closures, forgotten holiday schedules or pandemic reductions from three years ago. Advertising 10pm when you close at 9pm teaches customers to distrust the site and call, burdening them and staff.
Show hours in at least two places: homepage and Contact/Location page. Google-readable labels display them directly in Search/Maps. Match your Google Business Profile: conflicts may cause Google to display the less-trusted, wrong schedule.
Make addresses tap-to-navigate in Google Maps or Apple Maps. Keep reservation/ordering links in navigation and the mobile hero without scrolling. Hunting for Reserve loses diners.
What a restaurant website needs to do
A restaurant site has a tighter job than most small business websites. It's not trying to explain a complex service or educate a slow-moving buyer. It's answering six specific questions from a person making a fast, mobile decision. Each one either works correctly or it becomes a reason to choose somewhere else.
A menu page, not a PDF
Phone-friendly menus load under a second: brunch, lunch, dinner, happy hour, drinks and desserts, with Google-readable names, descriptions and current prices. Edit specials, 86'd dishes and prices in a simple file without technical skills/developer calls. Optional vegetarian, vegan, gluten-free and nut tags help guests pre-check restrictions.
Location, hours, and contact
Prominent hours include Google-readable labels for Search/Maps. Add Google Maps/Apple Maps navigation links, tap-to-call and landmark/intersection directions, such as "parking garage on 5th." Show hours in at least two places, homepage footer and Contact/Location page, so visitors can find them from any entry page.
Reservations and ordering: visible immediately
Integrate or prominently link OpenTable, Resy, Toast, Square Online or DoorDash Storefront in navigation and at the mobile page top, before scrolling. Diners can reserve/order as soon as they decide. Third-party integrations cost nothing extra.
Fast food photography
Food photos are the heaviest, most decisive restaurant content. Modern formats preserve quality in smaller, device-sized files; lower photos load on scroll. The main photo loads first, under a second. Result: a clean pass on Google's mobile speed/stability checks, supporting local rankings and keeping diners engaged through the menu.
Local SEO built in from the start
Google-readable labels identify name, address, phone, location, cuisine, prices and payment methods. Match every fact to Google Business Profile and name/address/phone across pages; submit a sitemap at launch. Searchable dishes expand reach for "best Thai near downtown" beyond PDFs/hosted menus. Restaurant local search combines strong intent with strong competition.
Events, specials, and private dining
Publish happy-hour days/times, rotating weekly specials, holiday prix fixe menus, private-dining inquiries with capacity/A/V/minimum spend, and live entertainment schedules. They encourage return visits and refresh search content. Event labels can show dates/times directly in Google results, free visibility most restaurant sites miss.
Ordering and reservation integration: what works and what to watch for
Most restaurants need ordering/reservation platforms. Broken widgets, hidden links and slow mobile embeds lose customers ready to transact. Evaluate each integration for an easy purchase or booking.
Online ordering platforms
The right ordering integration depends on what POS system you're running and whether you want delivery, pickup, or both. The major platforms at the independent restaurant scale:
- Toast Online Ordering : the natural choice if you're already on Toast POS. Orders flow directly into the kitchen display system with no manual re-entry and no tablet relay. The storefront can be built into your site or linked out to a Toast-hosted page. Commission-free for orders placed through your own domain (commissions apply for orders sourced through Toast's marketplace). If you're on Toast, start here — the ordering experience is tightly integrated with your actual kitchen workflow.
- Square Online : tight integration with Square POS and Square Payments. The ordering page can embed under your own domain or live as a Square-hosted storefront linked from your site. Strong for counter-service, fast-casual, and cafes already running Square terminals, where the payment flow is already Square-native. Less suited to full-service restaurants with table-assignment complexity.
- DoorDash Storefront : DoorDash's white-label ordering product. Customers order through your branded storefront, DoorDash handles delivery logistics, at a lower commission rate than appearing on the main DoorDash marketplace. Worth considering if you want to offer delivery without building your own driver network or contracting a separate courier. The storefront embeds cleanly or links from your site with minimal setup.
- Yelp Online Ordering : integration for restaurants already active on Yelp with meaningful review volume. Lower reach than Toast, Square, or DoorDash Storefront for direct orders, but useful for capturing customers who discover you through Yelp reviews and want to order without switching to a different app or site. Works best as a secondary channel, not a primary ordering solution.
Reservation platforms
For table reservations, the two platforms that matter most at the independent restaurant scale are OpenTable and Resy. They're not interchangeable.
- OpenTable : the highest-reach reservation marketplace in the U.S. A strong OpenTable presence with a high Diner Score and substantial review history drives a meaningful share of discovery for restaurants in competitive markets. The OpenTable widget embeds cleanly in most site layouts and loads without significant delay. Per-cover commissions apply for covers sourced through OpenTable's marketplace; direct bookings from your own site may be commission-free depending on your plan tier. If you're in a market where diners habitually use OpenTable to find restaurants (most major cities), not being on it is a meaningful visibility gap.
- Resy : popular with independent full-service restaurants, tasting menu formats, and chef-driven concepts that want more control over the reservation experience. Smaller marketplace footprint than OpenTable but a more polished product for managing the guest experience and communicating with diners before their visit. The Resy widget embeds well and the brand has strong recognition in the fine dining and independent restaurant segment. If your concept skews experience-first over volume, Resy fits the positioning better than OpenTable.
- Yelp Reservations and Waitlist : the third option, most useful for restaurants where Yelp is already a top traffic source. The waitlist integration pairs with the reservation widget. Worth adding if your Yelp listing drives a meaningful number of visitors and you want to capture them without requiring a redirect to OpenTable or Resy.
Build it in or link out: the tradeoff
Every platform lets you either build the ordering or booking step right into your page, or send people out to the platform's own page with a link. The right call is not the same for every platform or every restaurant.
Embedding keeps branding consistent through order/booking confirmation, improving completion without a disorienting departure. Toast and Square Online embed reliably; OpenTable's booking step is stable and fast.
Link out when embeds slow loading, fit phones poorly or offer a worse experience than the platform page. Use prominent, branded "Order Online"/"Reserve a Table" buttons at the top and in navigation, opening a new tab. Clear labels match existing intent; choose the easiest path to completion.
Commissions compound indefinitely: 200 monthly orders averaging $35 with a 6 percent commission cost $504 monthly. An ArdinGate Studios ordering app gives you ownership, direct customer data, promotional push notifications and distinctive branding without per-order fees or a shared DoorDash Storefront template. Bundle site/app; launch the faster site first, then the app when volume justifies it.
Making a food-photo-heavy site fast on mobile
Food photography sells your restaurant to new diners, but can quickly ruin mobile performance. Photos need enough size to look good without slowing the site. Here's how to preserve both quality and speed.
A modern image format that's far smaller
Photographers/phones still use decades-old formats. A modern equivalent preserves phone-screen quality while reducing 2.8 megabytes to 1.2 to 1.6 megabytes. Six homepage food photos plus twenty gallery images shrink from 65 megabytes to roughly 28 megabytes before further optimization.
Chrome, Safari, Firefox and Edge have supported the format for years; rare older browsers automatically receive the original. Convert once during the build and serve ready-made files automatically: no add-ons, services or loading overhead.
Each device gets a right-sized photo
A desktop food photo spans roughly 2,560 pixels. Sending it to a phone to shrink wastes more than six times the image data its screen can display.
Store multiple sizes and deliver the one matching each screen. For full-width restaurant hero photos, this cuts initial mobile downloads by 40 to 60 percent without harming appearance. Most Squarespace/basic WordPress restaurant sites send full-size images everywhere, explaining their mobile slowness.
Photos load as visitors scroll, so the page feels instant
When someone opens your restaurant's homepage, there's no need to download every single photo on the page right away. All that matters at first is the handful of photos on screen — the one up top, maybe one or two more. Everything further down the page is told to wait and load only as the visitor scrolls toward it.
For a hero, twenty-photo gallery and menu images, load the three visible images first, not all twenty-three. The remaining twenty arrive just before scrolling reaches them, making the page feel fast from the first second.
Fast-casual/build-your-own menus may pair each of 60 items with a photo. Loading on scroll fetches only the viewed section instead of all 60 immediately, even if diners never pass the first three sections.
Your main photo loads almost instantly
Google measures when the largest visible element appears, usually your main food photo. This mobile ranking factor directly affects a restaurant's local search position.
Three steps put the main photo onscreen in under a second on a typical phone connection: load immediately, mark it highest priority, and start fetching before the rest of the page finishes assembling. Every main-photo page on this site gets that head start automatically.
Put the photos next to the menu, not off in a separate gallery
Photo placement affects orders. A text-only menu and separate gallery force someone reading about duck confit to navigate elsewhere to see it. That extra step causes drop-off, a common restaurant-site mistake.
Put representative photos beside menu sections or high-margin dishes so description and image immediately create appetite. Food bloggers/local journalists prefer linking these useful menus over plain homepages or galleries. Those links build rankings for searches such as "best pasta in [city]."
For the standalone gallery, organize imagery by category (brunch dishes, dinner entrées, desserts, cocktails, interior, private dining space, events) so someone looking for a specific type of food or venue shot finds it quickly without scrolling through an undifferentiated grid. Each category should have its own anchor that event planners and bloggers can reference directly.
Pricing
Single-page menu/location/hours/contact/ordering or reservations: from $1,200. Multi-page brunch/lunch/dinner/happy-hour menus, gallery, events/specials, private-dining form and platform integration: $2,800–$5,000, depending on pages/integration complexity. Every build includes business labels, Google Business Profile review, name/address/phone consistency and sitemap submission at no extra charge.
Hosting starts at $60/month: nightly backups, SSL renewal, uptime monitoring. Care ($100/month) adds one hour of monthly menu/hours/specials/event edits: email changes, live within 24 hours. Most Care restaurant owners never send a separate menu-change invoice.
Common questions
How much does a restaurant website cost?
Single-page menu/location/hours/contact/ordering or reservations: from $1,200. Multi-page brunch/lunch/dinner/drinks/dessert menus, gallery, events/specials, private-dining inquiries and platform integration: $2,800–$5,000, depending on page count and platforms configured/tested.
Every build includes business labels, Google Business Profile review, consistent name/address/phone and launch-day sitemap. Hosting starts at $60/month for nightly backups, SSL renewal and monitoring; Care ($100/month) adds one hour of monthly menu/hours/specials edits without per-change invoices. Full pricing breakdown →
How do I update the menu after the site goes live?
Two workflows: Care ($100/month) includes menu edits within monthly content hours. Email/text new items, 86'd dishes, prices or seasonal swaps; live within 24 hours, without tickets/logins. Most owners prefer this to website work at 11pm after closing.
Alternatively, edit a lightweight PHP file listing menu sections, items, descriptions and prices: open any text editor, change, save. No technical knowledge, website login or subscription portal. Both workflows fit your kitchen, from quarterly seasonal changes to daily specials.
Can you integrate online ordering or reservations into the site?
Yes, at no extra cost. Ordering: Toast Online Ordering feeds Toast POS orders to KDS; Square Online suits Square Payments counter-service/fast-casual; DoorDash Storefront offers white-label delivery below marketplace commission; Yelp Online Ordering serves Yelp-driven traffic. Reservations: OpenTable/Resy embed cleanly; Yelp Reservations and Waitlist suit Yelp-heavy restaurants.
The integration method — embed vs. link — gets decided based on which performs better on mobile for your specific solution. If you eventually want to eliminate per-order commissions by owning the ordering relationship directly, a custom ordering app through ArdinGate Studios is the upgrade path. The website and app can be built as a bundle or in sequence.
Will the site help the restaurant rank in local search?
Every build includes Google-readable name/address/phone/hours/location/cuisine/price labels, Google Business Profile fact checks, name/address/phone consistency across pages, and launch-day sitemap submission. Mismatches undermine trust in site and profile and can display wrong information.
Restaurant searches such as "best Thai near downtown" or "romantic restaurant open late" signal immediate, committed decisions. Google Business Profile drives broad-query map placement; site labels reinforce it and expand dish/private-dining/neighborhood/event rankings. Fresh events and rotating specials sustain competitive local visibility. What's included in SEO setup →
How fast can a restaurant site be built?
Single-page restaurant sites (menu, hours, location, and an ordering or reservation link) deliver in 1 to 2 weeks from content handoff. Multi-page sites with a gallery, events section, private dining page, and platform integration take 3 to 6 weeks depending on page count and integration complexity.
Content usually controls timing: unfinished seasonal menus, pending food shoots and ordering/booking access delays (including Toast/OpenTable approval queues). Ready menus, photos and hours support the shorter timeline. A free scope call sets dates against actual readiness, avoiding commitments dependent on unresolved content or access.
How do you make a food-photo-heavy site load fast on mobile?
Four things working together. First, every food image is converted to a modern format that's far smaller without looking any worse — 30 to 50 percent smaller than the usual format. A homepage with six photos up top and a 20-image gallery goes from roughly 65 megabytes to about 28 megabytes before anything else below even touches it.
Second, size photos per device. Third, load lower photos as visitors approach them, fetching only visible content initially. Fourth, load the main food photo first for near-instant display. Google uses its appearance time in mobile rankings, directly affecting local placement and perceived speed.
What content do I need to provide to get started?
Provide menu sections/items/descriptions/prices (PDF, printed-menu photo or spreadsheet; rebuilt as a clean webpage), hours/address, usable food/interior photo rights (your dining-room shots, not another restaurant's stock food), logo/colors/fonts, and ordering/reservation logins for configuration and pre-launch testing.
Include specials boards, private dining menus, events calendars, and catering inquiry processes too. Menu descriptions, section introductions, and about copy are drafted from your materials and edited for accuracy; you need not start from scratch. Gathering content usually stretches timelines. Once it's ready, the build moves fast.
Also building for: catering companies · hotels, inns & B&Bs · contractors & home services · all small businesses
Your food deserves a site that doesn't lose people before they walk in.
You share what you're running — POS, reservation platform, how many pages, whether the photos are ready; I scope it and give you a number.
Get a quote