Dinner
Tacos, steaks, seafood and sides from the dinner kitchen.
LEÑA RESTAURANT
Fire from our heritage

LEÑA RESTAURANT
Leña’s fire, family and full table deserve a website that seats them as well as the dining room does. One clear front door for menus, hours, reservations and takeout.
We reviewed the restaurant’s public site and the page it calls its “main website” on a phone, at 100% zoom. Five things send a hungry guest somewhere else before the first plate reaches the table.
1
2
Two red “View Main Website” buttons point to http://www.lenaalameda.com — a different domain, on plain HTTP. The destination is a GoDaddy one-pager: ad, cookie wall, intro, contact form. No menus. No hours. No reservations.
The copy promises reservations and takeout. Across seven public pages: 0 reservation links, 0 ordering links. The only actions are a phone number and a contact form.
Source: href census · home, about, dinner, brunch, dessert, gallery, contactDinner, Brunch and Dessert total roughly 1,050 words of prose, with 0 item lists and 0 prices. A guest who wants to choose a dish has to call and ask.
Source: /dinner · /brunch · /dessertThe homepage references 16 PNGs totalling 9.15 MB; the hero image alone is 3.16 MB. On a phone on Central Avenue, the first impression is a loading screen.
Source: image Content-Length headers · 31 Oct 2026The contact page asks for image verification before a message can be sent, and the site publishes no email address. A dinner question should not feel like a security check. Also observed: the meta description repeats the restaurant name and the page title almost verbatim; Contact is titled “Seafood Restaurant.”
Source: /contact · HTML headThis is the path a guest can take today, built only from the public pages. No step required a login; every link and every missing link is real.
The cost is not a metric we can see from outside. It is the guest deciding whether the extra step is worth it — or trying the next restaurant on the street.
A working concept built with Leña’s own logo, the original storefront photograph and published hours. Use the tabs, then open the readable detail view. Menus, a table request and takeout all live in one place.
Mexican food, steak, seafood and a full bar — cooked with fire, served with family warmth.
Three choices above the fold, all the way down to a phone. Your team keeps the final word on every request.
The final dishes and prices are supplied and approved by Leña. This concept shows how a guest would browse them — not a substitute for your menu.
Tacos, steaks, seafood and sides from the dinner kitchen.
Weekend plates from 9:30 to 1:30, with the full bar alongside.
A sweet finish, designed to be scanned in one screen.
Cocktails and beverages that pair with the menu.
Catering and large parties: call the restaurant. Nothing on this concept is booked automatically.
Dinner, brunch, dessert and the bar in one scannable place.
Requests are prepared, never promised; the kitchen confirms.
The phone is the front door, not a shrunken desktop.
Six pieces built around one owner-approved source of truth. Each exists to make the next action obvious — not to add another dashboard to your week.
Decide the leading address, redirect the other, and make every public link land on the same HTTPS home.
Guest outcome · one address to shareDinner, brunch, dessert and the bar as real pages, updated from one sheet your team controls.
Guest outcome · fewer “what do you have?” callsConnect the reservation tool you choose; route takeout to the kitchen phone with hours attached.
Guest outcome · the next step is visibleGoogle Business Profile hours, photos, menu link and location schema kept accurate as service changes.
Guest outcome · the right first impressionA simple request flow and owner-voice replies, plus seasonal gallery updates from real service.
Guest outcome · recent, honest proofLuis on a direct line, a monthly review and one clear queue for changes and questions.
Owner outcome · someone accountableUFG Works asked for a clearer front door. This before/after shows the approach we would apply to Leña: hierarchy, a single next step and a system that holds at phone width.
A visitor should know what the business does before deciding where to go.
Every link earns its place and points to a real next step.
Hierarchy and type survive the phone, not just the desktop.
A proposed sequence. The clock starts when scope, access and approved content are ready — not before. Launch day is day 10, then 60 days of keeping it current.
One 90-minute kickoff with Luis, then the decisions only Leña can make.
Design, build, review and release — with a phone test before anything goes live.
A 60-day growth window, then a simple monthly rhythm if you want to continue.
Every option starts with the same three-day strategy sprint. Scope is fixed in writing before work begins; the fee is quoted after a 20-minute scope call. No dollar figure is invented here.
For ending the split between the two current addresses and giving guests one clear place to act.
For making the new site discoverable and keeping the public profile as current as the kitchen.
For a team that wants the site maintained and improved, not handed over and forgotten.
What happens on the call: confirm the leading domain, the reservation route and the pages that matter most. You leave with a written scope and a fixed-fee quote — not a retainer you did not ask for.
Walk through what we found, open the concept on your phone, and decide what is worth doing first. No pressure, no obligation.

The fire is already there. Let’s make the front door match.
Use a suggested slot or choose any weekday. This prepares an unsent email to Luis — nothing is booked.
Requested times are subject to confirmation. No appointment is booked.