Tech Stack
Performance Metrics
Chrome UX Report field data, mobile, August 2026
Zaza Grill and Kebab serves Turkish and Mediterranean food in Toms River. Restaurant websites tend to fail the same two ways: the menu is a PDF nobody wants to pinch and zoom on a phone, and every booking or catering question turns into phone tag. The rebuild went after both.
The Solution
The site runs on Next.js and React with Tailwind CSS, exported as static files and served from Cloudflare Workers. The menu is real HTML, which means Google can read every dish and so can a screen reader. Photography of the dining room and the food does the selling, with the lunch special and the ordering link a single tap from the top of the screen.
Three inquiry paths feed the restaurant: table reservations, catering, and private events. Each posts to our own form handler behind Cloudflare Turnstile, which stops the bots without making a real customer prove anything. Restaurant and FAQ structured data give Google the hours, the menu and the common questions as data rather than leaving it to guess from the page copy. We also moved the domain and DNS onto Cloudflare, so hosting, records and certificates are all in one account.
Results
- Real-user Core Web Vitals in Google’s good band across the board: 1.7s LCP, 120ms INP, 0 CLS
- Menu, catering and events pages crawlable as HTML instead of locked inside a PDF
- Reservation, catering and event inquiries arriving by email with bot filtering in front of them
- Restaurant and FAQPage schema feeding the Google listing
- Domain, DNS and hosting consolidated on Cloudflare