Stay updated with our letter
Valuable perspectives on the latest trends and tips.
.avif)
The £8,000 Mistake: Audited 40 London Restaurant Websites
Forty London restaurant websites, one ordinary diner’s task: read the menu and work out how to visit. The original audit found a persistent gap between the character of the restaurants and the usefulness of their websites. Its strongest lesson is practical: make the information easy to reach before commissioning more decoration.
A restaurant can communicate warmth within seconds of someone walking through the door. Online, that first impression depends on a different set of details: a readable menu, a convincing view of the room, accurate service information and a clear next step. None requires a spectacular website. All require attention.
This article revisits Fit Design’s recorded review of 40 restaurant websites, organised into four groups of ten around Soho, Shoreditch, Covent Garden and Borough. Those are editorial groupings rather than strict neighbourhood boundaries: the list also includes places in Clerkenwell and Hackney. The restaurants were selected for the audit, not randomly sampled from London hospitality.
How to read the findings: the observations, ratings and Performance scores below belong to the original audit. They are not live measurements or a new assessment of each restaurant. Websites, menus, teams and trading arrangements can change. The £8,000 in the title is an illustrative revenue scenario, explained below; the audit did not measure lost bookings or establish a minimum financial loss.
What the 40-site audit recorded
The clearest pattern concerned menu presentation. Nine restaurants were classified as having HTML menus and two as combining HTML with PDFs. The remaining classifications involved PDFs, images, a modal route or an external social destination. A well-designed PDF can still be useful, but forcing every diner through a document is a different experience from offering a readable menu page.
| Recorded format | Restaurants |
|---|---|
| 25 | |
| HTML | 9 |
| HTML + PDF | 2 |
| Menu image | 2 |
| Modal route | 1 |
| Instagram redirect | 1 |
The categories reflect the original audit’s classification, not mutually exclusive technical capabilities. ZIMA’s modal, for example, led to a PDF. “Hybrid” means HTML and PDF were both recorded. These distinctions help describe the route a diner encountered; they do not prove that a particular file format caused a failed booking.
Across the 40 recorded rows, the mobile Performance average was 52.85, rounded to 53/100, and 17 sites scored below 50. The audit also recorded an average time to menu of 7.1 seconds and a slowest observed route of 14 seconds at ZIMA. Time to menu includes navigation and interaction, so it should not be confused with a page-loading metric.
The original SEO checks recorded 19 sites without schema markup, none with Menu schema, and 23 with weak, missing or broken meta descriptions. Five sites were flagged for significant technical issues in the reviewer’s notes. These are findings to investigate, not a calculation of search traffic lost. Missing markup and a broken booking link are also different problems with different remedies.
The recorded Google review average was 4.48 out of five. That is a reputation measure, not a controlled food-quality assessment. Likewise, a Lighthouse Performance score is not a combined Core Web Vitals score or a percentage of satisfied visitors. Putting the two numbers beside one another illustrates different dimensions of the business; it does not create a causal relationship between them.
What the £8,000 example actually means
Consider a hypothetical independent restaurant serving 80 covers per night, six nights per week, for 50 weeks. That produces 24,000 annual covers at the assumed operating level. At an illustrative £55 spend per person, the associated annual revenue is £1.32 million. These are inputs to an example, not averages measured across the audited restaurants.
At an assumed 1%, the same arithmetic gives £13,200. Changing the percentage changes the result immediately, which is why the assumption matters more than the apparent precision of the total. A fully booked restaurant may replace a lost booking; another may have spare capacity only on particular services. A responsible business case needs those operational details.
The original article linked the widely repeated claim 53% of mobile users abandon a page that takes longer than three seconds to load. That historical statistic should not be treated as a current restaurant-specific conversion rate, and it cannot be applied directly to the audit’s time-to-menu observations. A visitor waiting for a page and a visitor navigating several menu choices are not necessarily experiencing the same delay.
A higher average spend at a London Michelin restaurant would increase the value of a cover in an equivalent hypothetical calculation. It would not prove that more covers were lost online. To estimate impact for your own restaurant, connect the website journey to completed reservations where measurement permits, then consider occupancy, cancellations and service capacity.
The practical question is therefore narrower and more useful than “is our website costing £8,000?” Ask where a diner gets stuck, whether that issue is reproducible, and what evidence would show that a repair helped. A verified booking failure deserves attention even before its annual financial effect has been modelled.
How the original review approached the websites
The audit followed a simple visitor task: arrive on a phone, find the menu and try to book or understand the visiting arrangement. Its notes combined technical checks with editorial judgment. That combination is useful because an automated score cannot explain whether a restaurant sounds appealing, while visual impressions alone cannot diagnose a loading problem.
Technical checks covered headings, page titles, descriptions, canonical URLs, Open Graph information, structured data, robots directives, image alternatives and the apparent platform. Mobile observations included menu access, booking visibility and Mobile LCP. PageSpeed Insights supplied separate Performance, Accessibility, Best Practices and SEO categories.
Read these as a snapshot. The retained article does not provide enough run-by-run detail to reproduce every timing under identical device, network and cache conditions. The qualitative comments are the reviewer’s assessment of what was visible, not evidence about an agency’s competence, a restaurant’s budget or the intentions of its team.
The earlier draft also connected restaurant closures with a six-week audit window. Without a consistent supporting timeline, that should not be used as a closure-rate statistic or evidence that websites caused businesses to close. This review concerns the recorded website experience. It does not assess the commercial health of the restaurants.
Soho: the menu route makes the difference
The Soho group shows how differently restaurants can approach the same task. A daily PDF may reflect an established kitchen routine; a web menu may reflect a deliberate publishing choice. The important comparison is whether diners can use the result and whether the team can keep it current. The ten profiles below retain the audit’s recorded menu formats and scores, with the observations separated from their implications.
Sussex
The reviewer found four PDF menus on a separate subdomain and described the mobile documents as blurry and difficult to read. Dense copy, alignment and spacing added to the difficulty. The useful first task would be to inspect the menu files and page layout together, rather than attributing the whole experience to a subdomain. A separate host may add a connection, but the audit notes alone do not establish its contribution to the recorded performance result.
ZIMA
The recorded route took 14 seconds on 4G and opened a PDF in Google Drive through a modal. The reviewer also found little material about the restaurant, staff or atmosphere. That combination creates two distinct projects: simplify access to essential information and improve the explanation of the place. The original claim that the menu was invisible to all search systems goes beyond the evidence. Access and rendering need direct investigation before making that conclusion.
Hoppers Soho
The menu opened as a Google Drive PDF that the reviewer found difficult to read on a phone. A secondary font had weak contrast, and an image slider relied on clickable dots rather than supporting the expected swipe interaction. These are concrete interface observations, not reasons to discard every part of the site. Improving the menu route, text contrast and gallery controls would provide a focused starting scope, followed by another test of the complete mobile journey.
Lobos Meat & Tapas
The audit recorded an HTTP visit with a browser security warning, alongside a difficult mobile PDF and text laid over imagery. It also found little context about the restaurant. The connection issue should be checked in a current technical review before discussing visual polish. A historical observation does not establish the site’s present security configuration. Separately, readable text and a clearer account of the offer would help visitors understand the restaurant without relying on the menu download alone.
Bocca di Lupo
The daily PDF showed an active menu-publishing routine, which is an asset to preserve. The reviewer nevertheless found the menu awkward on a phone, with a large font, a three-line announcement above the hero and an uneven arrangement of images and text. The opportunity is to carry the same approved daily information into a more usable presentation. Calling the document invisible to search would be too strong; the recorded issue was the experience of reaching and reading it.
Quo Vadis
Four prominent calls to action above the hero competed for attention, while the menus remained daily PDFs. The reviewer described a text-heavy page, limited imagery and a shop page without listed products. The lesson is about hierarchy: several large buttons do not necessarily make the next action clearer. Review which decisions a visitor needs to make first, then arrange menu access, reservations and any secondary commercial offers around that sequence instead of giving everything equal prominence.
Kiln
Kiln had the highest recorded Performance score, yet the editorial assessment described an unstructured image grid, inconsistent image sizing, missing captions and a difficult mobile presentation. The notes characterised the site as largely dormant since 2020. That contrast is instructive: a fast page can still communicate very little. The score does not explain why the site was fast, and the apparent age of content is not access to its maintenance history. Assess current accuracy and usefulness separately.
BAO Soho
The audit identified an HTML menu and a lighter, more scannable homepage. It also noted an awkward three-button row on location pages and heavy text over one image. This was a stronger menu example, not a flawless site by definition. The useful direction is to preserve the readable information while refining local hierarchy and contrast. A modern implementation still needs careful content decisions, especially where several locations or competing actions share the same template.
Andrew Edmunds
The handwritten PNG menu gave the site a distinctive visual character, but the reviewer found it difficult to read on a phone. Other notes concerned mobile responsiveness, several steps to booking and heavy text without supporting visual storytelling. The description of the site as untouched for roughly a decade was an impression, not a verified development history. A redesign brief should retain the restaurant’s character while providing usable menu text and testing the booking route with real devices.
Barrafina Dean Street
The recorded HTML menu was comprehensive, and booking remained visible. The main criticisms concerned an older-feeling visual treatment and text placed over hero imagery inside a box. This is a useful example of separating functional strengths from styling preferences. Preserve the clear menu and reservation access, then test whether changes to contrast, typography and image placement improve reading. Rebuilding the entire content system would require a stronger reason than the reviewer’s impression that the design looked dated.
Two Soho entries—BAO and Barrafina—were recorded with HTML menus. That is a useful contrast with the other eight routes, but it is not proof that bespoke technology caused a better outcome. The deciding work is often editorial and operational: agreeing how menu information is entered, approved, displayed and maintained.
Shoreditch and nearby: a modern stack is not a content strategy
This group includes different kinds of restaurants and several locations beyond a strict Shoreditch boundary. The common lesson is that technology does not write the story or organise the page. Café Cecilia and Rochelle Canteen supplied the two recorded HTML menus in this group; Brawn’s journal was a separate editorial strength, not a third HTML-menu example.
Smoking Goat
The homepage was described as Instagram-linked imagery with little explanatory text. The menu was a PDF, and the reservation route sat inside the hamburger navigation rather than appearing as a clear action on the page. The reviewer saw similarities with Kiln’s presentation. A useful content brief would explain the food and visiting arrangement while retaining the visual character. It should not assume that a shared appearance proves identical technical limitations or the same amount of editorial investment.
Brat
The homepage required a choice between two restaurants, and the reviewer wanted more context before that decision. Image sizing and menu branding were described as inconsistent, while reservations led to another page. A location chooser is not inherently unnecessary: it can help prevent visitors booking the wrong venue. The design question is whether each choice is understandable and whether a diner can reach the appropriate menu and reservation route without guessing what the two destinations mean.
Café Cecilia
The HTML menu was a positive finding, but the surrounding one-page layout lacked a clear hierarchy in the reviewer’s assessment. The original comparison with BAO used the apparent technical stack to show that similar technology can produce different experiences. The practical lesson survives without ranking the developers: organise the content around the diner’s questions. A simple page can work well when it distinguishes the menu, service details and next action instead of giving every piece of information the same treatment.
The Clove Club
The notes described a homepage centred on a clove illustration, limited supporting sections and tasting-menu wording referring to pre-pandemic pricing. Reservations required two clicks and the PDF was delivered through an API route. The technical route alone does not make the document unusable; the important checks are access, readability and accuracy. In a current review, verify the pricing language first, then decide whether the page explains enough about the experience before asking a visitor to reserve.
Rochelle Canteen
The audit found an HTML menu, a substantial wine list and navigation that remained visible. It also described dense welcome, about and team copy, with an email address rather than a contact form. The absence of a form is not automatically a defect if the contact route works and suits the restaurant. The stronger design task is to organise the substantial information so readers can scan it, understand the offer and make contact without losing the useful detail already present.
Som Saa
The reviewer recorded mobile-layout difficulties, an oversized logo and limited explanation of the restaurant. Five separate PDFs were hosted on CloudFront. The hosting service is not itself a diagnosis; the menu journey and files need assessment in context. A focused improvement could make the page hierarchy clearer and connect the food, room and visiting information. Before replacing the platform, check whether the current templates and editing process can present that material in a more coherent way.
The Quality Chop House
Eight PDF menus with timestamped filenames were recorded, along with broken feasting-menu links and slider navigation the reviewer initially missed. The notes also questioned the prominence of careers material and the absence of a footer. Broken menu access is a more immediate issue than either stylistic preference. Preserve the active publishing effort, repair the failing route and make the controls understandable. A restaurant’s long history can support its story, but it does not by itself prescribe a particular layout.
Brawn
The booking action opened a dedicated page, and the journal suggested ongoing editorial activity. The reviewer nevertheless found little explanatory copy or gallery material and described the overall design as dated. The useful opportunity is to connect existing publishing to the restaurant’s main visitor journey. A journal does not substitute for a readable menu or practical visiting information, but it can contribute character when its relevant material is easy to discover from the pages prospective diners actually use.
Bistrotheque
The audit described motion that interrupted reading and a deployment problem that left an unresolved variable in the homepage title. It also found a disjointed scrolling experience. The technical error should be treated separately from an opinion about animation: verify and repair the title output, then test whether the movement obstructs ordinary tasks. More content is not necessarily the answer. A calmer sequence, clear headings and accessible controls may make existing information much easier to use.
Galvin La Chapelle
There were useful food images and substantial information, but the reviewer noted repetition across pages and a pop-up that reopened after dismissal. The about content emphasised the chef more than the founders, and several images had empty-looking alternative-text placeholders. Review those images by purpose rather than assuming every empty alternative is wrong. The strongest immediate fixes concern repeated interruption and information organisation; the website already contained material that could support a more coherent reading experience.
Some sites offered useful material but made it difficult to scan; others gave the visitor very little to work with. Neither condition is solved by choosing a platform from a shortlist. Begin with the visitor’s questions and the restaurant’s publishing responsibilities, then judge whether the implementation supports them.
Covent Garden and the wider group: practical information needs a voice
The original Covent Garden grouping includes Sessions Arts Club in Clerkenwell. Keeping that distinction visible matters: the group is a way to organise the audit, not a claim about the restaurant’s address. Across these ten entries, the most instructive contrast is between useful story content and the details that still interrupt reading or booking.
Sessions Arts Club
This Clerkenwell restaurant appeared in the audit’s wider Covent Garden group. The page was described as a minimal, hero-led presentation with mobile-layout issues and a reservation control close to the hamburger menu. Private-event information was supplied as a PDF. Minimalism is not automatically a failure, but the controls still need space and the offer needs enough explanation. Test what a new visitor can learn and complete before deciding whether additional sections or a different structure would be useful.
Balthazar London
The reviewer liked the images, copy and design of the menu document, while noting awkward overlap in the hero and competition between newsletter sign-up and booking. Nine PDFs were recorded. That is a substantial document collection, although Roast’s twelve mean it was not the largest in the full audit. The practical task is to make the relevant menu easy to identify and read, then ensure secondary sign-up prompts do not obscure the visitor’s primary decision.
Cora Pearl
Named staff, press references and a more distinctive voice made this one of the stronger editorial examples for the reviewer. Its HTML menu was another positive finding. The concerns were more specific: repeated image-and-paragraph arrangements, an uneven mix of illustration and photography, and prices that blended into the menu text. Preserve the useful story while improving contrast and rhythm. Strong writing still benefits from a layout that makes the essential details easy to pick out.
Spring
The HTML menu was easy to find, but the reviewer described a sparse, illustration-led homepage and limited supporting material across linked pages. Reservations were located within the hamburger navigation. The contrast is useful: making menu text available solves one problem without necessarily explaining the wider experience. Assess whether visitors can understand the food, setting and service arrangements, then make the next action clear. There is no need to add sections simply to fill space if the content does not help that decision.
Rules
Rules combined HTML and PDF menus and was judged positively for its text, imagery and page sections. The original suggestion that the site was three to five years old was an estimate, not a verified build date or a reason by itself to redesign. This example demonstrates that a historic identity can coexist with practical online information. A current review should preserve the useful menu options and judge any proposed refresh against actual reading or maintenance problems.
The Ivy West Street
The reviewer rated this as one of the strongest overall experiences, citing an HTML menu and a comprehensive booking route. Those are useful observations, but the further inference that a collection platform necessarily forced structured data is not established by the notes. Treat the site as a recorded example of a coherent journey rather than a universal model. The relevant question for another restaurant is which decisions were made clear and whether its own operating arrangement needs the same approach.
Frog by Adam Handling
The audit found useful content, sections and a strong first-person voice. Three PDFs covered tasting, lunch and wine, and there were no persistent menu or reservation controls. The original entry recorded specific meal prices, but those historical figures should not be treated as current offers. A focused review would test menu readability and action visibility while preserving the established voice. Sticky controls are an option to evaluate, not a requirement that every restaurant page must adopt.
Petersham Nurseries Café
The pages contained useful material, but the menu’s illustrative type treatment made reading harder in the reviewer’s assessment. Other notes concerned mobile responsiveness, booking visibility and on-page SEO. These issues point towards careful refinement rather than a conclusion that the content has no value. Test the actual menu at phone size and enlarged text, review the important page fields, and decide where an action should appear based on the page journey rather than a universal sticky-button rule.
Henri at Henrietta Experimental
This was the first Webflow implementation identified in the audit, and its descriptive image alternatives received a positive mention. The reviewer still found mobile-layout issues, menu and booking actions hidden in navigation, and a PDF menu. It is a useful counterexample to platform-based promises: selecting Webflow did not automatically produce a web menu or the clearest action hierarchy. The improvement brief should name those specific requirements and test their implementation, rather than treating the technology label as the outcome.
Bancone Covent Garden
The recorded concerns included a difficult hero slider, three PDF menu sections, a placeholder-like file name and an embedded map needing attention. Reservations opened on a separate page. That final behaviour may be appropriate if the destination is clear and works well; it is not inherently a failure. Investigate the media and menu route, distinguish cosmetic naming from actual access problems, and verify that a diner can reach the correct booking destination without losing context.
Cora Pearl, Spring, Rules and The Ivy West Street were recorded with HTML or hybrid menus. Their wider site experiences differed, which reinforces the need to assess the whole journey. A readable menu does not automatically make navigation, imagery, contrast and booking equally successful.
Borough: help a first visit become an informed decision
The Borough group contains both concise one-page sites and more extensive restaurant websites. For each, a useful question is whether someone unfamiliar with the venue can understand how a visit works. Walk-ins, queues, reservations and multiple locations need clear explanations; they should not all be forced into the same booking-button template.
Padella
The daily-changing HTML menu was a useful publishing example. The reviewer also noted a hero video, location cards, a simple one-page structure and a Dojo virtual queue. For a walk-in-led arrangement, the goal is not automatically a persistent reservation button. Make the queue or arrival process understandable and clarify differences between locations. The absence of a conventional footer is a design choice to assess against missing information, rather than an independent measure of whether the site works.
The Garrison
Booking remained visible and the reviewer found good written content. The main concerns were inconsistent section design, images disrupting the layout and a PDF menu. This is a case for preserving strengths while repairing the reading experience. A clear booking route should not be lost during a redesign, and existing useful copy should inform the new structure. Test image behaviour at different widths and make the menu usable before deciding whether broader stylistic changes justify a larger project.
Casse-Croûte
The menu appeared through an Instagram image embed, and the homepage included a shopping-cart icon that the reviewer considered a distraction. The original notes also recorded a robots.txt concern. That technical finding needs a current check of the actual directives and affected URLs before drawing an indexing conclusion. Separately, provide usable menu information and clarify the primary navigation. An image embed may support the visual character, but it should not be the only route to essential text.
José Pizarro Bermondsey
The notes distinguished a wine PDF from food information available on an in-restaurant chalkboard. They also recorded a last blog post in September 2024, an awkward map route and inconsistent presentation across location pages. An inactive blog does not prove that every operational detail is out of date. The useful review is to check each venue’s current information, make the food offer understandable online and establish which elements should be shared across the group versus specific to a location.
40 Maltby Street
The recorded “View Menu” link redirected to Instagram, while the website itself offered little explanatory material. The reviewer described a minimal single-page site that appeared to have received limited subsequent attention. That impression should not be mistaken for maintenance records. The practical opportunity is to give diners a dependable source of menu and visiting information on the restaurant’s own site, while allowing social publishing to remain part of its communication rather than carrying the whole task.
Restaurant Story
The reviewer found useful information beneath several animations and described motion as an obstacle to the experience. The menu was a PDF, and booking visibility did not persist while scrolling. The first question is whether visitors can read and operate the page comfortably, including with reduced motion preferences. The original assertion that the PDF was invisible to AI search was not demonstrated. Improve the observed interaction and menu access without promising a particular search or recommendation outcome.
Roast
Roast offered images, video and an FAQ addressing dietary questions, which the reviewer regarded as a strength. Twelve PDFs formed the largest recorded menu collection, and the mobile Performance score was low. Those observations do not establish that the amount of copy caused slow loading. Investigate the actual resources and scripts while organising the menu choices clearly. Preserve useful answers, and ensure dietary information is accurate and maintained rather than shortening it solely to make the page look lighter.
Hawksmoor Borough
The HTML menu, visible booking action and metadata were all positive findings in the original review. The main reservation was the length of the page. A longer page does not automatically need a slider: headings, navigation and a clearer sequence may preserve useful information with less interaction. This is a strong example to study for the connection between menu access and booking, while still testing whether the amount and arrangement of content suit the reader’s immediate task.
The Anchor & Hope
Five HTML menu pages with dishes and prices were recorded alongside a downloadable option. The homepage, however, contained unfinished metadata and a hero treatment the reviewer found poorly proportioned on mobile. The original contrast between good menus and an “invisible” homepage was rhetorical, not a measured indexing finding. Keep the useful menu structure, finish the page information and test the opening layout. Different parts of the same website can require very different levels of intervention.
Elliot's Café
The audit described a basic two-location site with large text blocks, limited content hierarchy, no clear calls to action and seven PDF menus. The recorded platform was Squarespace, but those choices do not demonstrate that the product cannot support a better arrangement. Start with location clarity, menu access and the intended visiting route. A focused content and layout revision may answer those needs; migration requires a separate assessment of the editing and integration requirements that remain unsupported.
Padella, Hawksmoor and The Anchor & Hope supplied the three recorded HTML or hybrid examples in this group. The differences around them show why a single score or format label is insufficient. A menu can be well structured while the homepage is unfinished; a visually rich site can still make menu access unnecessarily complicated.
Five menu patterns—and what to do about them
The original audit arranged menu formats into a hierarchy of failures. A more useful reading is to treat them as different sources of friction. Their effect depends on the implementation, the information available elsewhere and the diner’s needs. Fix the observed difficulty rather than assuming every PDF or external link is equally harmful.
A PDF as the only menu
Twenty-five entries were classified as PDFs. Some were updated frequently, including Bocca di Lupo’s daily document. That publishing effort is valuable; the opportunity is to make the same approved information usable in a web page as well. A downloadable version can remain for people who want to save or print it.
Google can index PDFs, so “invisible to search” is too broad a conclusion. Inspect the real document and access route. Small text, a poor reading order, a heavy download or a missing connection back to booking can each be a more concrete problem than the format alone.
A modal or external document adds extra steps
ZIMA’s recorded route passed through a modal to Google Drive; Hoppers also used a Google Drive PDF. An external destination is not automatically inaccessible to a crawler, but it can disrupt the visitor’s context. Test what opens, whether it requires an account, how it behaves on a phone and how the diner returns to the restaurant.
The 14-second observation at ZIMA identifies a route worth simplifying. It does not establish a universal abandonment threshold. If the same information can be offered directly on a menu page, the design removes a dependency and gives the restaurant more control over the reading experience.
A photograph carries information that needs a text equivalent
Andrew Edmunds’s handwritten PNG and Casse-Croûte’s Instagram menu image preserve a particular visual character. The design challenge is to retain that character while making the dishes and prices available as usable text. A visitor should not need to decipher a photograph to obtain essential information.
The original discussion linked this to an Equality Act concern. That link provides legal context, not a legal finding about either restaurant. The practical accessibility task is to review the actual content and interaction with appropriate expertise. A photograph’s existence alone is not enough to assess a website’s legal compliance.
A social account becomes the only menu destination
At 40 Maltby Street, the recorded “View Menu” action led to Instagram. Social publishing can be part of a restaurant’s communication, but it should be a deliberate dependency. Consider the visitor who cannot access the platform, does not want to sign in or cannot tell which post contains the relevant menu.
Maintain a useful source of menu information on the restaurant’s own website where possible, and use social channels to distribute it. The benefit is consistency and access, not a promise that moving text automatically generates more bookings or search citations.
There is no usable online food menu
The José Pizarro Bermondsey notes distinguished a wine PDF from food information available on the restaurant’s chalkboard. A daily-changing offer can make exact advance publication difficult, but the website can still explain the style of food, the changing-menu arrangement and how guests can obtain current information.
Be explicit if an online menu is a sample. Do not solve an information gap by publishing dishes or prices that the kitchen cannot stand behind. The right arrangement balances accuracy, workload and the diner’s need to make an informed choice.
The larger gap: the website does not explain the place
Menu access was the easiest pattern to classify. The deeper editorial issue was harder to score: many pages provided limited explanation of what made the restaurant distinctive. A guest could sometimes find an address and a reservation route without learning enough about the room, cooking or occasion to decide whether it suited them.
A restaurant’s history can contribute to that explanation, but age is not the only worthwhile story. A small new opening may have a clear point of view, a particular style of service or a thoughtful approach to its ingredients. The task is to identify real details and present them in a way a prospective diner can understand.
Good photography works alongside that writing. A room at service communicates something different from an isolated plate; an entrance image solves a different problem from a chef portrait. Give each image a job. Avoid burying useful pictures in a gallery that visitors must discover after several unrelated clicks.
The original review highlighted Cora Pearl’s stronger voice and references to people behind the restaurant. Its screenshot is retained above as an example from the audit, not a claim that the current website looks identical. Notice the underlying editorial question: what can someone learn here that helps them imagine a visit?
A brand refresh may be useful when the language and presentation no longer reflect the restaurant. It need not mean inventing a grand new narrative. Interview the team, clarify the offer and organise the material around the questions diners ask. The resulting pages should feel specific to the place rather than interchangeable with every restaurant in London.
The eleven HTML and hybrid examples
The following platform descriptions and menu classifications are retained from the original audit. They show that readable web menus appeared across several implementations. They are not endorsements, a current technology scan or proof that every other platform lacks the same capability.
| Restaurant | Menu | Platform |
|---|---|---|
| BAO Soho | HTML | Next.js + Sanity |
| Barrafina Dean Street | HTML | WordPress (bespoke) |
| Café Cecilia | HTML | Next.js + Sanity |
| Rochelle Canteen | HTML | WordPress (Elementor) |
| Cora Pearl | HTML | BentoBox |
| Spring | HTML | WordPress |
| Rules | HTML + PDF | WordPress |
| The Ivy West Street | HTML | Ivy Collection Platform |
| Padella | HTML | WordPress (custom) |
| Hawksmoor Borough | HTML | WordPress (multi-location) |
| The Anchor & Hope | HTML + PDF | Custom |
The list includes WordPress, Next.js with Sanity, BentoBox, a collection platform and a custom implementation. The original article also referenced Webflow as a restaurant-site option. Platform choice should follow the editing and integration requirements, not the assumption that one product automatically produces a better menu.
For example, Squarespace documents menu blocks. A PDF on a particular Squarespace site therefore describes a publishing choice or implementation, not proof of an unavoidable product restriction. Ask the team to demonstrate the required workflow before recommending migration.
What a useful improvement brief looks like
Begin with one complete diner journey. Someone arrives from search, checks the food, decides whether the restaurant suits the occasion and follows the appropriate booking or visiting route. Record the moments where information is missing or the interface becomes difficult. A screen recording and a short explanation can be more useful than a long list of subjective design complaints.
Then separate urgent repairs from broader development. Broken links, incorrect hours and unreadable menu information deserve clear ownership. A visual refresh can follow a coherent content plan. A rebuild becomes justified when essential requirements cannot be supported reliably within the current system, not simply because the site belongs to an older design trend.
For the menu, define the source of truth and the update process. Who approves a change? Who publishes it? Does a downloadable version need updating too? How is a sample menu labelled? Test those tasks with realistic content, including long dish names and several menu sections, before accepting the implementation.
For booking, follow the route into the reservation provider and back again. Check the location, date selection, unavailable dates and confirmation. A visible action is useful, but a completed task is the meaningful outcome. A walk-in restaurant needs equally clear guidance without being pushed into an unsuitable reservation model.
For search presentation, review SEO meta titles and meta descriptions alongside the actual page copy. Google may generate a snippet from page content; the text displayed in results is not necessarily the supplied meta description. Write accurate summaries rather than treating a fixed character count as the definition of quality.
Structured data should support accurate visible business information. Google’s Local Business documentation provides guidance for restaurant details and a menu URL. Validate the implementation and keep it consistent with current hours and locations. Markup does not guarantee a particular search appearance or AI citation.
For images, review the purpose before writing alternatives. The W3C guidance allows empty alt text for decorative or redundant images and calls for useful alternatives where an image conveys information. Replacing every empty attribute with keywords would create a new accessibility problem.
Finally, agree on a maintenance routine that fits restaurant operations. A new website should not depend on one person remembering every change. Give the team an understandable handover, recoverable access and a process for checking important updates. The quality of the launch matters; the quality of the next hundred small changes matters too.
What this means for restaurant owners
Fit Design builds bespoke Webflow websites, so our commercial interest is explicit. That does not make a rebuild the answer to every issue in this audit. A better menu workflow, focused technical repair or stronger content may be enough. The scope should follow the evidence and the restaurant’s ability to maintain the result.
The 40 entries are useful because they show the same visitor tasks handled in different ways. Take the relevant questions to your own site, verify the current problem and ask for a clear explanation of the proposed fix. Avoid buying a guaranteed search outcome or an invented revenue recovery figure.
If you want help turning those observations into a practical brief, we're here. If you handle the improvements with your existing team, the same standard applies: accurate information, usable menus, clear visiting arrangements and a website that communicates the place people are considering.
Investigate the actual URL, crawl and indexing settings, page content and access route. PDFs can be indexed, so the format alone does not explain absence from results. A readable HTML menu can improve the visitor experience without guaranteeing rankings or AI citations.
No. The £7,920 calculation assumes 24,000 annual covers, £55 spend and a hypothetical 0.6% difference. It is gross revenue arithmetic, not measured lost bookings, profit or a minimum loss across the restaurants.
There is no universal choice. Compare the actual menu-editing, location and booking requirements. The audit included several implementations, including WordPress. A PDF on a particular site does not prove that its platform cannot publish a web menu.
Use a phone to find the menu, understand the visiting arrangement and follow the reservation or queue route. Record reproducible problems and distinguish a click on a booking link from a completed reservation. Review actual results alongside service capacity and cancellations.
No. Relevant structured data can clarify accurate business details and should match visible content. Validate and maintain it, but do not treat Menu schema as a requirement for Google to read menu text or a guarantee of recommendation by an AI assistant.
.webp)
Where ideas come to life
We explore various aspects of modern life, offering valuable perspectives on the latest trends, and helpful tips.
