Where the project begins to go wrong
A QR code is only as effective as the page it opens. When a visitor taps a code on an exhibit label, retail shelf or event poster and lands on a page designed for a desktop browser, the interaction typically fails before any content is consumed. The visitor sees tiny text, misaligned columns, horizontal scrollbars or elements that do not respond to touch. Most will leave within seconds.
"Mobile-optimised" in this context means more than simply fitting on a smaller screen. A properly prepared landing page will have a viewport meta tag directing the browser to scale content correctly, text sized for reading without pinch-to-zoom, touch targets large enough for a finger rather than a cursor, and a layout that reflows into a single column. Images should be appropriately sized for mobile bandwidth, and any interactive elements—forms, buttons, expandable sections—must work with touch input alone.
The mistake occurs most often when a QR code is added as an afterthought to an existing web presence. A museum links directly to a collection page built for researchers. A retailer points a code to a product page on an e-commerce platform that has not been configured for mobile. An event organiser links to a PDF timetable that renders as a tiny, unreadable rectangle on a phone screen. In each case, the QR code itself works perfectly; the destination lets the visitor down.
There is a distinction between a page that is technically responsive and one that is practically usable on a phone. A page may reflow into a single column but still require excessive scrolling to reach the relevant information, or present navigation menus that obscure content on smaller devices. For proximity use cases, where the visitor is standing in front of an exhibit or product, the page needs to deliver its core message within the first screen or two, without forcing the user to hunt through sections designed for desktop browsing.
Prioritise causes by risk and evidence
Retail environments
In a shop, a QR code on a shelf edge or product display typically serves a clear purpose: show pricing, ingredients, stock availability or a short video. If the destination page is the standard desktop product page, the visitor encounters navigation bars, promotional banners, footer links and side panels before reaching any useful information. By that point, the moment has passed. The customer is standing in an aisle, not settling in to browse a catalogue.
Where the retailer controls the e-commerce platform, the solution is to create a dedicated mobile landing page or ensure the existing product page has a properly configured mobile view. Where the retailer is linking to a supplier's website, the situation is more difficult. The supplier's page may not be mobile-optimised, and the retailer has no control over it. In that case, the options are to host a short intermediary page on the retailer's own domain, to contact the supplier about mobile configuration, or to reconsider whether a QR code is the right channel for that particular information.
Museums and heritage sites
Museum QR codes often link to object records, audio files or interpretive text. Collection management systems frequently generate pages designed for desktop research. When a visitor scans a code next to a painting and receives a page full of catalogue metadata in small type, the intended educational outcome is lost. The visitor came for context, not a database entry.
A practical approach is to build lightweight mobile pages that pull key fields from the collection system—title, date, artist, a short paragraph of interpretation, perhaps an image—rather than directing visitors to the full record. If resources do not allow that, the QR code should at minimum point to a page where the most relevant text appears at the top, above any navigation or metadata.
Events and conferences
Event organisers frequently use QR codes to link to schedules, speaker biographies, floor plans or session feedback forms. Linking to a full conference website homepage is a common error. The visitor standing in a corridor wants the specific session detail, not the event's sponsorship packages. Linking to a PDF is another recurring problem. Even when a PDF is technically readable on a phone, the experience is poor: slow to load, difficult to navigate, and often formatted for A4 printing rather than a six-inch screen.
When you do not control the destination
Not every QR code points to a page the deployer owns. Regulatory compliance links, certification bodies, partner promotions and third-party booking systems are all common destinations. Before deploying a QR code to an external page, test it on at least two different mobile devices and operating systems. Check not only whether the page loads, but whether the information the visitor needs is accessible without scrolling past irrelevant content. If the external page is not fit for purpose, an intermediary page on your own domain that provides a summary and links out is often the only workable solution.
Confirming the fix and preventing recurrence
Assuming responsive equals usable
A content management system that applies a responsive framework does not guarantee a good mobile experience. The page may reflow correctly but still present desktop-oriented content structures: long introductions, multiple calls to action, dense paragraphs. For a QR code interaction, the page should be purpose-built or at least reviewed specifically for the mobile, in-venue context, not merely checked for responsive behaviour.
Linking to PDFs without mobile testing
PDFs are a frequent destination for QR codes in venues: menus, maps, timetables, safety information. A PDF that looks clear on a monitor can be unreadable on a phone. Text may be too small, the document may open in a viewer that does not support pinch-to-zoom well, or the file may be large enough to cause a timeout on a slow venue Wi-Fi connection. If a PDF is the only available format, check its file size, test its rendering on both iOS and Android devices, and consider whether a simple web page would serve the same content more effectively.
Ignoring load times on venue connectivity
Even a well-designed mobile page will fail if it takes too long to load. Venue Wi-Fi can be congested, and mobile signal strength varies considerably inside large buildings. Pages heavy with high-resolution images, embedded video or third-party tracking scripts may time out or appear to hang. Strip the landing page down to what is necessary: the core content, a readable typeface and minimal imagery. Test load times on the actual venue network, not just on a office connection.
Forgetting that the visitor is standing up
Desktop pages are read by someone seated at a desk, often with a mouse and keyboard. A QR code page is read by someone standing in a shop aisle, a gallery or a conference corridor, holding a phone in one hand. Long-form content, complex forms or anything requiring sustained attention is fundamentally mismatched to the physical context. The landing page should deliver its value in a few seconds of reading.
Key checks before deployment
- Viewport test: Open the destination URL on a phone. Does the text scale to the screen width without horizontal scrolling? If not, the page lacks a correct viewport meta tag.
- Touch target test: Can every link and button be tapped reliably with a thumb, or are they too small or too close together?
- Content priority test: Is the information the visitor actually needs visible in the first screen, or buried below navigation, headers and promotional content?
- Load time test: Time the page load on the venue's own Wi-Fi or mobile signal. If it takes more than a few seconds, the page needs to be lighter.
- Cross-device test: Check the page on at least one iOS and one Android device. Rendering differences between browsers can expose problems that are invisible on a single test device.
- Context test: Stand in the physical location where the QR code will be placed. Hold your phone at reading distance. Is the experience comfortable, or are you squinting, scrolling excessively or waiting?
If any of these checks fail, the QR code should not be deployed until the landing page is corrected or replaced. A functioning QR code that opens an unusable page is worse than no QR code at all: it wastes the visitor's time and damages trust in the technology for future interactions.
