Your PDF menu is driving hungry customers to your competitors.
I see it constantly with cafes and restaurants around Saltaire, Shipley, and Bradford. Someone searches “lunch near me” on their phone, taps through to a website, hits “Menu” — and gets a 3MB PDF designed for A4 paper crammed onto a six-inch screen. They pinch, zoom, scroll sideways, lose their place, and leave. They walk into the place next door instead.
PDF menus are unreadable on phones without zooming, invisible to Google search, slow to load on mobile data, and impossible to update quickly. They lose an estimated 20-30% of mobile visitors.
That's not a small leak. For a cafe on Victoria Road doing 200 website visits a week, that's 40 to 60 people who never see the menu properly. Some of those would have walked in.
Why can't customers read PDF menus on phones?
PDFs were built for print. They have fixed dimensions — typically 210mm by 297mm for A4. Your phone screen is roughly 70mm wide. The text shrinks to become unreadable, and there's no way around it without pinching and zooming.
Over 78% of restaurant searches in the UK now happen on mobile, according to Google's own data. If your menu doesn't work on a phone, it doesn't work for most of your audience.
Can Google index a PDF menu?
Technically, yes. Practically, poorly. Google can crawl PDF files, but it can't break them into structured sections the way it can with HTML. An HTML menu page with proper headings — starters, mains, desserts — lets Google understand and rank individual dishes.
Someone in Bingley searching “sourdough pizza Saltaire” could land directly on your menu if it's HTML. With a PDF, that search goes nowhere. Your menu is a black box to search engines.
How does a PDF menu compare to an HTML menu?
| Feature | PDF menu | HTML menu |
|---|---|---|
| Mobile readability | Requires pinch-zoom | Fits any screen automatically |
| Google indexing | Poor — treated as a single document | Strong — individual dishes are indexable |
| Typical file size | 2-5MB | Under 50KB |
| Load time on 4G | 3-8 seconds | Under one second |
| Update process | Edit source file, export, re-upload | Change text, save, it's live |
| Allergen info | Often a separate PDF download | Inline, tappable, accessible |
| Daily specials | Impractical to update daily | Takes two minutes |
The speed difference alone matters more than most owners realise. As I wrote about in my piece on first impressions and the first 50 milliseconds, visitors judge your site before they consciously process it. A slow-loading PDF kills that first impression.
Why are PDF menus so hard to update?
Updating a PDF menu means opening the original design file (if you still have it), editing it, exporting a new PDF, and uploading it to your website. Most restaurant owners in Shipley and Bradford don't have Adobe InDesign. They're stuck asking whoever designed it to make changes, which takes days and often costs £30-£50 per update.
An HTML menu page can be edited in minutes. Prices change? Update the number. Dish sold out? Remove it. Seasonal special? Add a new section. No design software, no waiting, no extra cost.
What if I like the design of my PDF menu?
Keep it. Offer it as a downloadable option for the few people who want to print it at home. But make the primary menu — the one on your website — an HTML page that works on every screen.
Think of the HTML version as the experience, and the PDF as the backup. Around 80% of your visitors will never download the PDF if the HTML version is clear and well-structured.
What should a good restaurant menu page include?
- Clear sections (starters, mains, desserts) with anchor links so people can jump around
- Dish names in at least 16px font — readable without zooming
- Short descriptions that make the food sound worth ordering
- Prices in plain text, not hidden in a decorative font
- Allergen markers inline, not buried in a separate document
- Fast loading — under one second on a 4G connection
I build menu pages for cafes and restaurants around Saltaire and Bradford that hit all of these. It's not complicated, but it does need to be done properly.
What's the best alternative to a PDF menu?
An HTML menu page on your website. It's readable on every screen, indexable by Google, loads instantly, and you can update prices in minutes.
Some restaurants use third-party platforms like Facebook or Deliveroo as their main menu. That's better than a PDF, but you're sending traffic away from your own site and losing control over how your food is presented. Your website should be the single source of truth.
Does switching from PDF to HTML actually help?
Restaurants that switch from PDF to HTML menus typically see a 20-40% increase in time-on-page. More time on the menu means more people deciding to visit. For a change that takes a few hours to build, that's a strong return.
I've seen it locally too. A cafe near Roberts Park switched from a PDF to a proper HTML menu and noticed more midweek bookings within a month. They couldn't prove causation, but the timing lined up.
If you run a restaurant, cafe, or takeaway anywhere in Leeds, Bradford, or the wider Yorkshire area, check your website on your phone right now. Tap your menu link. If a PDF opens and you have to pinch to read it, your customers are doing the same thing — and some of them are leaving.