Creating a website for a restaurant in Brussels: the guide

Too many Brussels restaurants still display their menu as a downloadable PDF. On a smartphone, it’s a disaster: you have to zoom, scroll every which way, and often wait several seconds for the file to open. The reality is that most of your potential customers leave before even reading a single dish.

A lightweight, responsive HTML menu page solves everything. It loads instantly, adapts to the screen, and can be structured with anchors (starters, mains, desserts) for quick browsing. Add well-compressed photos and a clean layout: the customer sees the essentials without friction.

Take a cue from places that display their daily specials directly, with the option to pin certain dishes. It’s more engaging than a static PDF that gets forgotten and never updated.

Integrating a booking widget (Formitable, Zenchef, Resengo) directly into your site provides a smooth experience: the customer never leaves your page and completes their booking in a few clicks. This reduces drop-offs, as every redirect to an external platform creates a break in trust.

The downside is the weight: some widgets slow down loading. At KRUZ, we always deliver a working prototype before any contract is signed so you can test real-world speed. A hybrid solution is to integrate the widget only on a dedicated page, asynchronously, so it doesn’t block the rest of the site.

If you’re just starting out, a simple redirect to a Formitable form may be enough, as long as the link is clearly visible. But as your business grows, native integration becomes a real conversion lever.

More than 80% of searches like 'Italian restaurant Brussels' or 'brunch Ixelles' end with a click on the Google Business Profile (GBP) or the website. Your GBP listing must be complete: precise hours, professional photos, a link to the menu and booking. Consistency between the name, address, and phone number (NAP) on your site and on GBP is crucial.

A fast, well-structured site also boosts your local SEO. Google favors pages that load quickly, especially on mobile. Consider embedding a native Google Map and using Schema markup for restaurants, so your hours and reviews appear directly in search results.

Encouraging your customers to leave a Google review is one of the most underrated levers. A site that aggregates these reviews or links to them elegantly gains instant credibility.

First mistake: unoptimized photos. High-definition images taken by a talented chef are great, but if each file weighs 5 MB, your page will take forever to load. Compress them without visible loss and use modern formats like WebP.

Second mistake: hiding the menu. Too many sites require you to click 'Download the menu' or fill out a form before you can see the dishes. The menu should be accessible with a single click from the homepage, ideally visible without excessive scrolling.

Third mistake: hard-to-find hours. If a visitor has to search for more than three seconds for your opening hours, they'll assume you're closed and look elsewhere. Put them at the top of the page or in the header, and repeat the info on a dedicated page.

A quality brochure site with a responsive menu page and a booking link typically costs between €2,500 and €4,000 excl. VAT. If you want native booking integration, a custom design, and thorough SEO optimization, the budget climbs to between €4,000 and €7,000 excl. VAT. These figures reflect the work of a serious provider, not a €40 template.

Be wary of offers under €1,500: they often hide a rigid site, poorly optimized for local search, that will be outdated in 18 months. Conversely, a studio like KRUZ prioritizes a working prototype from the start: you see exactly what your site will look like before signing the contract.

Also consider ancillary costs: hosting (around €150 to €300 per year), the domain name (€15/year), and possible updates if you're not self-sufficient. A realistic budget includes these costs with no surprises.

According to Google, 53% of mobile visits are abandoned if loading takes more than 3 seconds. In the restaurant business, that figure is probably higher: a hungry customer won’t wait. Every extra second eats into your bookings, especially at peak times.

The solution comes down to three principles: lightweight code, no unnecessary animations, and optimized images. A static or headless site, with no heavy database, can load in less than a second. That’s the approach we favour at KRUZ, because speed is a Google ranking factor as much as a conversion driver.

Test yours with PageSpeed Insights: if you come in under 2 seconds, you’re top of the class. If not, it’s time to revisit your work. A restaurant that’s fast in the kitchen should be fast online too.