Bianco's Pizzeria

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.

Role Freelance UX Designer & Researcher
Client Bianco's Pizzeria, Walpole MA
Tools Hotjar · Clarity · Tilda CMS
Status Ongoing, Phase 2
Impact

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.

Problem

The homepage had two equal CTAs. The food menu got twice the taps. That path had no exit to ordering.

Premise

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.

Context Insight Design Results What's Next Reflection
At a glance
1
The constraint
Conversion happens on a third-party platform. The moment a user leaves the website for Speedline, all tracking stops. Every metric in this project is a signal, not a confirmed sale.
2
The decision
Two equal CTAs were replaced with one. The static menu page, the primary dead end, was redirected to Speedline. Both paths now lead to ordering. Users who had been hitting a wall were picked up and placed directly into the ordering flow.
3
What the data showed
Visits ending with a click to the ordering platform went from 25% to 41.5%. Order button taps went from 11.3% to 33.3% of all taps. The share of CTA taps hitting a dead end dropped from 57% to zero. No platform rebuild. Copy, hierarchy, and redirect only.
Context

Strong product, loyal customers, a website in the way

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.

01
Complete, January 2026
Research & Redesign
  • Behavioral audit via Hotjar and Clarity
  • Unmoderated user study (3 participants)
  • Single CTA replacing competing buttons
  • Click-to-call phone number
  • Business info moved above the fold
  • Cookie banner and chat widget removed
02
In Progress, 2026
Validation & Measurement
  • Menu page redirected to Speedline (March 5)
  • 30-day post-redirect data window open
  • Tracking gap investigation underway
  • CTA language comparison across three variants
  • Post-redesign user test planned
03
Planned
Growth & Brand
  • SEO and Google Business Profile optimization
  • Brand story content strategy
  • Social media and marketing calendar
  • Platform evaluation (Tilda vs. purpose-built)
Insight

Users weren't avoiding ordering. They wanted to see the food first.

Menu button taps
19%
OUR MENU, hero button
Order button taps
10%
ORDER NOW, only path to Speedline
Hamburger nav taps
27%
Led to food menu overlay
Dead element taps
2,641
Sessions hitting elements that didn't respond

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.

Legacy homepage CTAs with Clarity hotspot overlay
The two CTAs, legacy site. Equal visual weight, side by side. OUR MENU captured nearly twice the taps. Users reached for the menu first, not the order button.
Legacy static menu page
Where OUR MENU led. Underlined headers that look like links. Tapping them does nothing. No photos, no prices, no path to ordering. This is where most sessions ended.
Path 1: What most users did Legacy flow
Google Search
Intent: Quick lunch order
Bianco's Homepage
PAIN POINT: Two equal CTAs. Wrong path wins.
Taps "OUR MENU"
54% of CTA taps went here
Static Menu Page
PAIN POINT: No photos, no prices, no path to ordering. Confirmed dead end.
Scrolling / Tapping dead links
PAIN POINT: Underlined headers that look like links. Tapping them does nothing.
Exit
Order lost
Path 2: What the site intended Optimal path
Google Search
Bianco's Homepage
Taps "ORDER NOW"
Speedline Ordering Page
Order Placed
Conversion success
Two paths, one dead end. 54% of CTA taps went to a page with no way to order. The other 46% reached Speedline.

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.

Rage click, legacy site. A user trying to reach the restaurant taps the "Place an Order" heading in the footer and then the phone number below it, and neither responds.

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.

S
"OOOHH PICTURES. Definitely makes me want to buy more."
Shosh. Excited by homepage photos; visibly deflated when the food menu had none
A
"When I was browsing the menu, I just saw a ton of text. With food, I usually expect to see an image."
Abby. Also asked for ratings and "highly ordered today" signals to speed up decisions
W
"The Order Now button could be right there so I can order while I'm looking at the menu."
Wilson. Found no way to start ordering from within the food menu

The structural constraint

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.

Why not a richer menu on the site?
The redirect was the right first move, not the final answer. Sending menu traffic to Speedline picks up users who were hitting a dead end. What comes next depends on data. Phase 3 may scope a visual category menu on the site, with each section linking directly into Speedline. The constraint: it can't require maintaining two separate menus. Whatever gets built links to Speedline.

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.

Design

Every decision traceable to a specific finding

Same Tilda CMS, no platform rebuild. Each change is grounded in what the data showed.

Mobile, legacy vs. redesign comparison
Mobile, legacy vs. redesign. Left to right: hero, specials section, contact and location. Full-viewport hero with hidden CTAs vs. single order button above the fold.
What changedWhy
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.
Results

Visits ending with a click to ordering nearly doubled

What we measuredBefore / After
Visits ending with a click to ordering25%/41.5%↑ Nearly 1 in 2
CTA taps landing on a dead end57%/0%Eliminated
Share of all taps on the order button11.3%/33.3%↑ 3×
Users returning for a second visit13.1%/29.6%↑ Doubled
Hamburger nav dependency (mobile)30.9%/19.7%↓ 11pts
Taps on non-responsive elements19.2%/15.8%↓ Fewer dead ends
Frustrated repeated tapping17 sessions/TBDPost-redirect data April 5
Users immediately returning to Google13.4%/9.5%↓ Fewer mismatches
Single-page visits27.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.

Reflection

The most important calls were interpretation calls

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.

On AI in this project: The legacy audit and problem identification came before any AI tools were introduced. Claude was used to synthesize the volume of behavioral data across Hotjar and Clarity, maintain a living project document, and build this case study page. The goal: more time on the judgment that requires a designer, less on work that doesn't.