Restaurants & brasserie

Grand Café du Commerce

No framework, no CMS: a neighbourhood brasserie doesn't need a factory.

Year
2026
Design & build
2 weeks
Stack
HTML/CSS · JavaScript · Google Analytics · Vercel
  • Design
  • Development
  • Local SEO
  • Audience measurement

Demo version put online by Kayzen Web at a Vercel address; the final domain belongs to the client.

https://grandcafeducommerce.vercel.app/
Home page of the Grand Café du Commerce website — Restaurants & brasserie, built by Kayzen Web
Lighthouse performance
93/100
external dependencies
0
requests on top of the HTML
2
Lighthouse SEO
100/100
The starting point

What needed solving.

The background

Le Grand Café du Commerce is a brasserie in Vaise, in Lyon's 9th arrondissement. Neighbourhood customers, lunchtime regulars, evening diners.

The constraint

The previous site was a single page, not responsive, with out-of-date opening hours. The real need fitted in three lines: the menu, the opening hours, a way to book. Anything more would have been spending with no return.

The response

HTML, CSS and a little JavaScript. No framework, no CMS, no database. The result loads instantly, needs no security updates and costs nothing to host. The menu is edited in a plain-text file.

Measured, not claimed

The scores recorded at delivery.

Lighthouse scores for the live site. We publish them as they are: when one is low, its cause and the plan to fix it are set out below rather than glossed over.

PageSpeed
93
Performance: 93 out of 100
97
Accessibility: 97 out of 100
100
Best practices: 100 out of 100
100
Search engine optimisation: 100 out of 100
Design & art direction

Every design choice, and the reason for it.

  1. A brasserie register, not a fine-dining one

    Assertive typography, a burgundy and cream palette, photos of simple dishes. Branding that was too chic would have driven away the lunchtime crowd, which brings in the most revenue.

  2. Opening hours on the first screen

    “Open until 10 pm”, calculated live, rather than a seven-row table. It is the most frequently asked question, and it deserved an answer rather than a document to interpret.

  3. The menu in HTML, never as a PDF

    A PDF menu cannot be read on a phone, is not indexed and is not announced to screen readers. The menu is a structured HTML page, with its prices.

Project palette

  • Burgundy

    #6E2436

    Identity, headings

  • Cream

    #F6F0E4

    Background

  • Ink

    #211E1C

    Text

  • Brass

    #B08A4A

    Rules and details

Type system

Display

Libre Baskerville

Body text

Source Sans 3

A classic serif, in the spirit of brasserie signage, for headings only — body text stays in a screen sans-serif.

Engineering

What's under the bonnet.

  • HTML/CSS
  • JavaScript
  • Google Analytics
  • Vercel
  1. Zero dependencies

    No library to update, so no vulnerability to patch in six months' time. For a restaurant website that will not be maintained every month, it is the most responsible choice.

  2. One CSS file, one JS file

    Two requests on top of the HTML. The site is complete before a framework-based site has finished parsing its bundle.

  3. Audience measurement with consent

    Google Analytics only loads after explicit acceptance. Without consent, no third-party script is called — not as a nicety, but because that is the rule set by the CNIL (France's data protection authority).

Search engine optimisation

How the site makes itself findable.

  1. “Brasserie Vaise”, “restaurant Lyon 9”

    Local search targets the neighbourhood before the city: competition there is ten times weaker and intent ten times stronger.

  2. Structured opening hours

    openingHoursSpecification in JSON-LD: this is what feeds the “Open · Closes 10 pm” shown by Google, and it saves customers a phone call to check.

Accessibility

Usable by everyone.

Since June 2025, the European Accessibility Act has required digital accessibility from a large share of online services. We build it in at the design stage rather than retrofitting it.

  1. 97/100 without any retrofitting

    A simple site is easier to make accessible. Semantic HTML, checked contrast, native keyboard navigation: nothing to fix after the fact.

Site structure

What was delivered.

  • Home
  • The menu
  • Book
  • Directions and opening hours
  • Contact
Method

How the project unfolded.

  1. Scoping

    Three needs identified, everything else set aside.

  2. Design

    Brasserie register, live opening hours, HTML menu.

  3. Development

    Dependency-free HTML/CSS/JS, consent before measurement.

Questions

What we are often asked.

Because a five-page site that changes twice a year does not need a database, an admin back end and monthly security updates. WordPress would have cost more to host and maintain, for a slower result.

The same high standards, for your website.

A free audit of your current site, a quote within 24 hours and written reasoning — like the case study you have just read. Pay in three interest-free instalments; local funding schemes checked before you sign.

Share