A general website builder gives you a home page, a contact form and a PDF upload. The menu goes in as a picture, the table booking goes to a widget from somebody else's platform, and the ordering goes to a marketplace that keeps a share of every bill. Three logins, three bills, and a site that Google reads as a brochure, not as a restaurant.
We checked 1,000 independent UK restaurant websites with the same engine behind our free checker. Of the 755 that loaded, 77% had no usable Restaurant schema, 31% had no meta description, 35% had no H1, one in ten published the menu as a PDF only, and 13% sent orders to a commission-charging marketplace. Those are not design problems. They are what happens when a restaurant is squeezed into a tool built for everyone.
A restaurant website builder should start from the menu, treat bookings and ordering as pages of the same site, and ship the search configuration without a technician. That is what TableSpark builds, for £19 a month excluding VAT, with nothing to pay until the site is published.