The ordering button ranked third on its own homepage. Behavioral data showed users reaching for the food menu first. That path had no exit to ordering. Redirecting that intent doubled the rate of visits ending with a click to the ordering platform.
More visits ending with a click to the ordering platform. Before: 1 in 4. After: nearly 1 in 2.
Before the redesign, 57% of ordering CTA taps went to a dead end. After: zero. Every tap on an ordering button now reaches Speedline.
The homepage had two equal CTAs. The food menu got twice the taps. That path had no exit to ordering.
Users weren't avoiding ordering. They wanted to see the food first. The fix wasn't removing the menu path. It was making both paths lead to Speedline.
Bianco's is an independent, woman-owned thin-crust pizzeria in Walpole, MA. They run their own delivery drivers. It was a deliberate choice to stay off Uber Eats and DoorDash and protect their staff. The product is strong. The local reputation is strong. The problem wasn't awareness.
Most orders still came in by phone, creating operational load and removing visibility into customer behavior. 75% of sessions were on mobile. 65% arrived via Google search. Active intent, not casual browsing. A hungry parent on a weeknight doesn't need to be sold. They need one tap to ordering. The site gave them a fork in the road instead.
The engagement runs across three phases. Phase 1 (research and redesign) is complete. Phase 2 (validation and measurement) is in progress.
The homepage had two buttons side by side: OUR MENU and ORDER NOW. OUR MENU got nearly twice the taps: 19% of all site-wide clicks versus 10% for ORDER NOW. The mobile hamburger accounted for 27% of all taps. Open it, and the first option was the food menu. Two taps to the same dead end.
The site had a systemic affordance problem: elements that signaled interactivity but delivered nothing. Menu headers were underlined like links but tapped to nowhere. The phone number looked like static text with no dialer behind it. The footer heading looked actionable but wasn't. Every false signal added friction the user couldn't diagnose.
The behavioral data showed two competing buttons and a menu path that led nowhere. The unmoderated user study added what the data couldn't: all three participants mentioned missing food photography without being prompted. Three strangers, one session each, same observation. When that happens it stops being an assumption. It's a finding.
One constraint shapes every measurement decision in this project: conversion happens on Speedline, a third-party platform. The moment a user leaves the Bianco's website, all tracking stops. Whether they placed an order is invisible. That meant the goal wasn't more traffic. It was less friction on the path to a platform we couldn't instrument.
The approach followed the user. 69% of hamburger-first sessions ended at the menu tap. Not because users were lost, but because they wanted to see what was on offer before committing. That is a reasonable, predictable behavior. The problem was where it led. Rather than redesigning the menu from scratch, the decision was to redirect that intent: anyone tapping Menu now lands on Speedline, which serves as both a browsable menu and an ordering system. Users who had been walking into a wall were picked up and placed directly into the flow they were looking for.
A consistent signal across both periods: roughly 1 in 5 mobile visitors navigates to the menu via the hamburger nav, regardless of what else changes on the page. That segment is not going away. It is a user need to serve better over time, not a problem to eliminate. Upcoming tests are designed with this in mind.
The menu redirect was a deliberate first step, not a final answer. Routing menu traffic to Speedline picks up users who were hitting a dead end and places them somewhere they can actually order. It buys time to gather data on whether the browsing need is being served, or whether a more intentional menu experience on the site is worth building. Phase 3 will answer that question.
Same Tilda CMS, no platform rebuild. Each change is grounded in what the data showed.
| What changed | Why |
|---|---|
| Two equal CTAs → single "Start Order" | OUR MENU got twice the taps of ORDER NOW. Eliminating the split removes the dead-end path. "Start Order" over "Order Now." The phrasing implies browsing is welcome, not that you must commit immediately. |
| Affordance failures corrected across the site | Three elements signaled interactivity but weren't interactive: the menu headers (underlined, looked like links), the phone number (static text, no dialer behind it), and the chat widget (styled like a messaging tool, generated 28 taps almost all from confused users). Each was either fixed or removed. The phone number became click-to-call. The chat widget was removed. The menu redirect resolved the dead end the menu headers were pointing toward. Restoring correct affordance signals was as important as the CTA hierarchy change. |
| Anonymous pizza grid → named, clickable specials | All three study participants independently cited missing food photography. Named items give first-time visitors a visual anchor before clicking through. |
| Business info → above the fold | Location, phone, and delivery area were hidden below a full-viewport hero with no scroll affordance. |
| CTA repeated mid-page | Scroll depth showed 50%+ of sessions reaching mid-page. The CTA needs to meet them there. |
| Cookie banner removed | No legal requirement for a US-only local audience. Removed friction and cleaned up data capture. |
| Food photos recommended for Speedline | At the start of the engagement, Speedline had no food photography: a long undifferentiated list with no visual hierarchy. Flagged to the owner as a friction point. The manager subsequently added photos to most menu items. Outside the website, inside the ordering experience. |
| Static menu page → redirected to Speedline | Session recordings showed users hitting dead ends across the static menu page: underlined headers that looked like links and did nothing, no path to ordering, no photos. The page absorbed traffic that had nowhere useful to go. Redirect completed March 5, 2026. |
| What we measured | Before / After | |
|---|---|---|
| Visits ending with a click to ordering | 25%/41.5% | ↑ Nearly 1 in 2 |
| CTA taps landing on a dead end | 57%/0% | Eliminated |
| Share of all taps on the order button | 11.3%/33.3% | ↑ 3× |
| Users returning for a second visit | 13.1%/29.6% | ↑ Doubled |
| Hamburger nav dependency (mobile) | 30.9%/19.7% | ↓ 11pts |
| Taps on non-responsive elements | 19.2%/15.8% | ↓ Fewer dead ends |
| Frustrated repeated tapping | 17 sessions/TBD | Post-redirect data April 5 |
| Users immediately returning to Google | 13.4%/9.5% | ↓ Fewer mismatches |
| Single-page visits | 27.3%/41.7% | Not abandonment The old site counted a menu tap as a second pageview, artificially lowering this number. A user who now lands, taps Start Order, and goes straight to Speedline completes in one page. The rise reflects the path working, not failing. |
Clarity, 100% session capture. January 6 – March 4, 2026.
| What | When / Status |
|---|---|
| Menu redirect evaluation | 30-day window closes April 5, 2026. Watching whether fewer sessions hit the old menu path and whether more visits end with a click to the ordering platform. |
| Google Business Profile menu card fix | After April 5. The GBP menu card currently routes through a Google search results page before reaching the site. Fixing it to point directly to Speedline removes a second dead end outside the website. |
| CTA language test | After April 5. Three labels currently in use across the site: "Start Order," "Order Now," and "Order." Will standardize to one label across all five buttons, run for 3-4 weeks, then rotate. Looking for language that captures both browsing and ordering intent. The 1 in 5 visitors who navigate to the menu first suggest the current phrasing may read as more commitment than browse. |
| Remove "Menu" from hamburger overlay | After CTA label test. Once button language explicitly signals that browsing and ordering happen in the same place, the overlay menu link becomes redundant. Catering and Contact Us remain. |
| Closing the tracking gap | Inquiry sent to the ordering platform. If it can receive tags from the website, it becomes possible to see which visits led to actual orders. That is the most important number in this project. |
| User testing, post-redesign | Planned: test the full path from homepage through Speedline ordering to surface remaining friction at the handoff. |
| Menu experience: Phase 3 decision | After the CTA label test. Two paths: if new button language captures the browsing segment and Menu nav taps drop, the Menu link gets removed from the hamburger overlay and eventually the nav entirely. If a meaningful share of users still seek a menu experience the CTA alone doesn't satisfy, a visual category menu page gets scoped, with each category card linking directly into that section in Speedline. That path depends on Speedline having stable category-level URLs, which is a reasonable dependency. Either way, the no-parallel-maintenance rule applies: any future menu work links out to Speedline, it never mirrors it. |
Longer term, there's a brand story that hasn't been told. Long-tenured kitchen staff. Their own delivery drivers. A deliberate choice not to join Uber Eats, made to protect livelihoods, not just margins. A content strategy rooted in that story, paired with SEO work and a marketing calendar, is the difference between a fixed website and a growing business.
Understanding what the tap data actually meant was the work. Why more single-page visits signaled improvement, why the food menu needed to be treated as user intent before it could be treated as a design problem: those were interpretation calls, not design calls. Working within a free-tier toolset, a third-party platform that couldn't be modified, and incomplete conversion data: navigating that clearly is the skill.
This was also my first time working in Tilda CMS and building a measurement practice from scratch. That meant taking analytics courses, learning how behavioral data tools work, setting up tracking and conversion events in Tilda, and finding my way around Clarity's recording and heatmap tools to pull signal out of raw session data. Claude became part of the workflow for evaluating CSV exports and synthesizing findings across large datasets. The learning happened alongside the work, and that was part of the work.