| Page speed and Core Web Vitals | Template dependent; image-heavy restaurant templates are the heaviest | Custom coded to a 90+ PageSpeed target, photography optimised as part of the build |
|---|
| SEO control | Solid fundamentals; deeper structure is manual work | Full control plus the page architecture built for you |
|---|
| Schema and structured data | Some built in; anything beyond it is a code injection | Generated from the visible content, kept in step with it |
|---|
| AEO and GEO readiness | Depends entirely on how the copy is written | Answer-first copy, visible FAQ blocks, llms.txt, consistent facts |
|---|
| Hosting and security | Included in the subscription | Included: edge hosting, SSL, CDN, DDoS protection, unmetered bandwidth |
|---|
| Maintenance burden | Yours, including every menu price and photograph | Ours, as revisions: 5 a month of any size, within 2 to 5 working days |
|---|
| Who does the work | You, or a designer you pay by the hour | A team on the plan you already pay for |
|---|
| Content and blog | Good blogging tools, empty until you write | 2 to 3 researched articles a week, written for your niche |
|---|
| Design quality | Strong out of the box, and recognisable as a template | Designed around your menu and brand rather than fitted to a layout |
|---|
| Accessibility and policy pages | Your responsibility | Accessibility-minded build plus restaurant-specific policy pages |
|---|
| Cost model | Subscription plus ordering app fees plus your time | One monthly fee, build fee after launch, ordering on your own domain |
|---|
| Lock-in and ownership | The design lives in their editor and does not transfer | Domain in your name, content export on cancellation |
|---|