NomiWebsite review

Nomi Thai Asian Dining · Hexham

The current site, and what a new one could do

A plain-English look at nomi.restaurant today, a list of what a new site could add, and three contrasting design routes to react to. Open each route on your phone as well as your desktop, and scroll slowly to see the animations.

The current site at a glance

nomi.restaurant is a single scrolling page. It has a “Now open” banner, the logo, two call buttons (bookings and takeaway), a tabbed menu, a service-status panel, opening hours, the address, a grid of 12 photos and a contact footer. There is also a hidden second page, /discover, which shows the most-ordered dishes from the till. It is built as a React app and served through Cloudflare.

What it does well

  • The phone numbers for bookings and takeaway are the first thing you see, and both are tap-to-call.
  • The full menu is on the page, with lunch, dine-in, takeaway and kids menus on tabs.
  • Restaurant structured data (address, phone, hours) is already in place for Google.
  • The /discover favourites page is genuinely original, well designed and scores 100 for accessibility.
  • It is served over HTTPS through Cloudflare, and the old domain redirects properly.

What holds it back

  • No online booking, ordering or vouchers. Everything is “call us” or “coming soon”.
  • To Google it is one page, titled just “Nomi”, with an empty body until JavaScript runs.
  • It is slow on phones: about 9 MB of photos, the largest 2.5 MB, all loaded straight away.
  • “Open now” is hard-coded, so it shows even when the restaurant is closed.
  • Every menu or price change needs a developer to rebuild and redeploy the site.
  • The /discover data feed exposes raw sales volumes, and the full source code is publicly downloadable. See the technical overview.

What a new site could have

Ordered roughly by impact on covers and revenue. All three design routes already show the first five in action.

Three design routes

The three routes are deliberately different, so it is clear which direction feels right. All three use Nomi’s real menus, prices, hours, photography and elephant logo. Every photo has been re-encoded as AVIF/WebP at up to four sizes, so a phone downloads an 87 KB version instead of the 2.3 MB original.

Built into all three routes

Scores

Google Lighthouse, mobile profile (simulated slow 4G on a mid-range phone). The routes are measured on this preview server; the current site is measured live.

Lighthouse mobile scores, current site vs. design routes
PagePerformanceAccessibilityBest practicesSEOLCPCLSPage weightRequests
Current site – Home61941001007.1 s0.2838.8 MB25
Current site – /discover6610096923.2 s0.539204 KiB21
Route A – Lantern971001001001.9 s0350 KiB12
Route B – Soi991001001002.0 s0.001330 KiB11
Route C – Jasmine991001001001.9 s0671 KiB17

Each route carries a canonical link to nomi.restaurant, so Google treats the live site as the original and won’t rank these previews against it.

Read the technical overview of the current site for how it is built, what the numbers mean and a prioritised fix list.

To confirm with Nomi