PDF menus vs interactive web menus: where static files fall short on a phone

We've already compared QR code menus and PDF menus from the owner's side: cost, updates, specials. This one is about the guest. What happens when someone opens a PDF menu on a phone, and what does the research say about it?

Why PDFs struggle on phones

A PDF is a fixed page. It was designed to look the same everywhere, and that's exactly the problem on a 6-inch screen. The text doesn't reflow to fit, so guests pinch, zoom and drag sideways to read a line.

This isn't only a restaurant problem. The UK government's digital service, which publishes for millions of people, stopped defaulting to PDF for this reason. Its 2018 explanation lists the problems: PDFs don't fit small screens, zoomed text doesn't wrap, readers lose the site's navigation, and PDFs are harder to keep up to date, so they go stale. Nielsen Norman Group, a user research firm, has argued for over 20 years that PDFs are unfit for reading on screens, and its 2020 update says the same problems follow readers onto their phones, where they have to pinch, zoom and scroll.

Accessibility

Some of your guests use screen readers or make text larger. In WebAIM's 2019 survey of 1,224 screen reader users, 75% said PDFs were very or somewhat likely to cause significant accessibility problems.

A well-made web menu is ordinary HTML: real headings, real text, and content that reflows when someone enlarges it. SpotMyMenu's themes are tested against the WCAG AA contrast standard in both light and dark mode.

Speed

Speed matters most in the seconds after a scan, when the guest is staring at a blank screen and the table is waiting.

Google's much-quoted figure is that 53% of mobile site visits are likely to be abandoned if a page takes longer than 3 seconds to load. It's worth knowing where that came from: an analysis of about 3,700 mobile sites in 2016, when networks were slower than today. A later Google analysis of 11 million ad landing pages found that as load time goes from 1 to 10 seconds, the chance of a mobile visitor bouncing rises 123%. The exact numbers are dated. The direction isn't: slower pages lose people.

A designed PDF with photos can easily run to several megabytes, and phones often have to download most of it before the menu is readable. A fast-loading mobile restaurant menu does the opposite. A typical SpotMyMenu menu page is about 10 KB compressed before photos. The text, prices and sections arrive first, and photos load as the guest scrolls. The dishes and prices even show with JavaScript turned off.

Search

Google can index PDFs and reads the text in them, as long as it's real text and not a scanned image. So a PDF menu isn't invisible. But it opens in a viewer without your site around it, and a scanned menu may not be readable at all.

On a web menu, dishes are plain text on a normal page. You can link it from your Google Business Profile, which has a menu link field, and from your website's structured data using the menu property Google documents for restaurants. One myth to ignore: Google has no special "menu" rich result, whatever some SEO blogs say. Our guide to adding your menu to Google walks through the setup.

What "interactive" actually adds

In an interactive web menu for restaurants, "interactive" just means doing things a fixed page can't:

• A section bar that follows the guest and jumps to Drinks or Desserts in one tap.
• Tap a dish to see its photo, full description and add-ons.
• Sold-out badges that appear as soon as you mark an item.
• Specials that appear and disappear on the dates you set.
• "Open now" or "Closed", worked out from your hours.
• English and Spanish with one tap, opening in the language the guest's phone uses.
• Tap to call, get directions or open your Instagram.

None of it asks the guest to download an app or log in. The scan opens the menu. You get the zero friction of a restaurant menu app without asking anyone to install one.

Measuring what you couldn't before

A PDF tells you nothing about who opened it. A web menu can. SpotMyMenu shows visits, time spent on the menu, the most viewed dishes and sections, and how many guests tapped to call, get directions or visit your website. It doesn't track orders or revenue. Those stay in your POS.

When a PDF is still the right call

If you need a printable version for catering or events, PDF is the right format for that job. Nielsen Norman Group's advice is the practical one: put the content in HTML, and offer a PDF download for people who want to print it.

For the menu behind your QR code, the one guests read at the table, use a page built for phones. Try SpotMyMenu free for 7 days, or follow our step-by-step guide to creating a QR menu.