How we score you.
The audit is directional, not a certification. Below is exactly how each question rolls up into your 0–100 readiness score, and where the underlying best-practices come from.
Scoring in three steps
- 01Each question yields a 0–100 sub-score derived from the answer chosen (or the sum of selected options in a multi-select).
- 02Sub-scores are averaged within their category. The mobile-UX category optionally blends a lightweight URL check (HTTPS, viewport, response time) at 30% weight.
- 03Category scores are weighted by real-world impact on scan-to-conversion and summed into the overall readiness score.
Category weights & sources
Design & Scannability
If it doesn't scan, nothing else matters. Contrast, quiet zone, minimum size and error correction are the fundamentals.
- · ISO/IEC 18004:2015 — QR Code specification
- · GS1 QR code quality guidelines
Placement & Context
The physical surface, distance, dwell time and lighting decide whether the code is scanned at all.
- · Field studies on scan-rate by placement surface
CTA & Value
The #1 published cause of low scan rates is missing or generic CTAs. A one-line benefit reliably lifts scans.
- · Uniqode 2024 QR benchmarks — CTA framing impact
- · Bitly 2024 QR benchmarks — CTA and incentive lift
Tracking & Analytics
Static codes are effectively invisible. Dynamic codes with UTMs are the difference between guessing and knowing.
- · Google Analytics 4 UTM attribution documentation
Mobile UX (Landing Page)
Every second of load time costs scans. Dedicated mobile-first landings out-convert homepages, PDFs and app stores.
- · Google web.dev — Core Web Vitals & mobile performance
- · Chrome UX Report — mobile abandonment vs load time
Security & Trust
Non-branded destinations and non-HTTPS pages increasingly trigger phone-side warnings and 'quishing' concerns.
- · FBI IC3 2023 QR phishing (quishing) advisory
- · Google Safe Browsing developer documentation