Zaza Grill and Kebab
Toms River, NJ
The old site looked polished, but its photos, its chefs and its reviews weren't Zaza's. The new one is built from what the owner sends us: his menus, his dishes, his corrections. Reservations, catering and job requests go straight to the restaurant's inbox.
Before (the site Zaza had until May 2026)
After (September 2026)
Zaza Grill and Kebab serves Turkish and Mediterranean food in Toms River. The site it had before looked good at a glance: dark, glossy food photography, a “Meet the Team” page with three chefs, and five-star reviews with faces beside them. But the photos weren’t Zaza’s dishes, the chefs didn’t work there, and the reviews didn’t come from its customers. A diner who walked in expecting that site would have found a different restaurant.
The new site is built from what the owner gives us: his printed menus, photos of his own dishes, and his corrections. Reviews are left to Google, where anyone can check them. We got one thing wrong first: our January draft still carried the old site’s three chefs. They came out the same day.
Running a restaurant leaves no time for learning a website editor, so the owner doesn’t. He sends a photo of a dish or a screenshot with something circled, and we take it from there.
What the site does
Restaurant sites tend to fail in two ways. The menu is a PDF nobody wants to zoom on a phone, and every catering or party question turns into phone tag. Here the menu is a real page with photos of his own dishes, and there are separate request forms for a table, catering, a private event, and a job, each landing in the restaurant’s inbox.
What they asked for, and what we did
-
In August he sent a screenshot with the lunch badge circled: it should say Monday thru Friday, not Daily.
Fixed the same day.
-
Same message: make the Google title "Best Turkish & Mediterranean Restaurant in Toms River".
Live that day. Google took its time showing it, which is normal; it re-reads a page when it gets to it.
-
He sent photos of his printed catering and group menus.
The catering and events pages were rebuilt to match them, prices included, the same day.
-
In September he sent 14 photos of dishes, with captions.
Every photo was matched to its dish by eye against his captions (the file names didn't follow the order he sent them) and put on the menu.
What's different now
- Reservation, catering, event and job requests arrive in the restaurant's email, with bots filtered out.
- The whole menu is a normal web page, so it reads on a phone without pinching and Google can see every dish.
- Real photos of his food on the menu.
- No made-up reviews. The site sends people to Zaza's Google listing, where real customers leave them.
- Opens quickly for real visitors on phones: 1.7 seconds to show the page, in Google's "good" range on every measure. Chrome UX Report, real mobile visitors, August 2026
Run a restaurant or diner in Monmouth or Ocean County?
Tell us what customers ask you most and what's not working now. We'll tell you what we'd change and what it costs.
Under the hood (for the technical folks)
- Next.js, exported as static files.
- We build our own systems that keep spam off our clients' sites, and customers never have to solve a puzzle to send a form.
- Restaurant and FAQ structured data feed his Google listing the hours, menu and common questions.
- Domain, DNS and hosting all in one place.
Built with
Speed (Core Web Vitals)
Chrome UX Report field data, mobile, August 2026