On this page
- 01Key takeaways
- 02What is the GBL Mobile Readiness Scorecard?
- 03How do you score each of the five tests?
- 04What does your total score mean?
- 05How does the score relate to Google's own measures?
- 06What are the limits of a scorecard?
- 07What does this look like in practice?
- 08Scorecard checklist
- 09Next step
- 10Sources and further reading
- 11Frequently asked questions
Key takeaways
A mobile website scorecard replaces opinion with a number. The GBL Mobile Readiness Scorecard tests five things on a real phone, Read, Tap, Speed, Act and Parity, each scored 0, 1 or 2. It takes about an hour, needs no specialist tools, and tells you whether to fix, redesign or leave alone.
- Five tests, 0 to 2 each, for a total out of 10.
- 8 to 10 is mobile-ready. 5 to 7 is usable but leaking. 4 or below is failing.
- Score on a real phone over mobile data, not in a browser on a laptop.
- Fix the lowest score first: one zero costs more than three ones.
Want a second opinion on your score? Send us your URL on WhatsApp and we will score it independently.
Chat on WhatsApp →What is the GBL Mobile Readiness Scorecard?
The GBL Mobile Readiness Scorecard is a five-part test of how well a business website works on a phone, covering readability, tap targets, speed, ease of action and content parity with desktop. Each part is scored 0, 1 or 2, giving a total out of 10 that can be tracked over time.
Global Bridge Labs (GBL) uses it at the start of website work because it is quick, repeatable and hard to argue with. Two people scoring the same site on the same phone should land within a point of each other. It is deliberately practical: every test is something a customer would experience, not a line in a technical report.
How do you score each of the five tests?
Score each test on your top three landing pages, using a phone on mobile data with Wi-Fi switched off. Give 2 when the test is fully met, 1 when it is partly met, and 0 when a typical visitor would struggle. Take the lowest score across the three pages for each test.
- Read: 2 if all text is legible without zooming and nothing scrolls sideways; 0 if you have to pinch.
- Tap: 2 if every button and link can be hit first time with a thumb; 0 if you mis-tap more than once.
- Speed: 2 if the page is usable in about 2.5 seconds; 1 if under 4; 0 if longer.
- Act: 2 if you can call, message or enquire in under a minute from any page; 0 if you have to hunt.
- Parity: 2 if mobile shows the same content as desktop; 0 if sections, links or pages are missing.
What does your total score mean?
A total of 8 to 10 means the site is mobile-ready: keep it that way with a quarterly re-score. A total of 5 to 7 means the site is usable but leaking enquiries, and targeted fixes on the existing site are the right response. A total of 4 or below means the site is failing on phones and needs a structural change.
- 8 to 10: maintain. Re-score every quarter and after any redesign.
- 5 to 7: fix in place. Indicative £500 to £3,000 of focused work.
- 4 or below: redesign or rebuild. Indicative £3,000 to £20,000 or more.
- Any single 0: fix that first, whatever the total.
Scored 7 or below? Message us on WhatsApp for a fix list in priority order.
Chat on WhatsApp →How does the score relate to Google's own measures?
The Speed test maps to Core Web Vitals, where Google's threshold for a good Largest Contentful Paint is 2.5 seconds at the 75th percentile of real visits. The Tap test reflects Google's web.dev recommendation of touch targets around 48 pixels with about 8 pixels between them. Parity reflects mobile-first indexing, under which Google indexes the mobile version of your content.
The scorecard is not a substitute for PageSpeed Insights or Search Console. It is the human check that sits alongside them. A page can pass every automated audit and still hide the phone number in the footer, which no tool will flag and every customer will notice.
What are the limits of a scorecard?
A scorecard measures the experience, not the outcome. A site can score 9 and still produce few enquiries if the offer is unclear, the prices are wrong or the traffic is poor. Use it alongside your conversion data: the score explains why mobile visitors struggle, and the data tells you how much it matters.
It also depends on the phone and connection you test with. A flagship handset on fast 5G hides problems that a three-year-old Android on patchy 4G will expose. If you can only test on one device, borrow the oldest phone in the office.
What does this look like in practice?
A pattern we see when owners score their own site for the first time: they expect a 9 and record a 5. Read and Parity pass, because the site is responsive and modern. Tap scores 1 because the menu links sit too close together. Speed scores 1 on mobile data. Act scores 0, because the only route to an enquiry is a contact page three taps away.
That profile is common and encouraging. Nothing in it needs a new website. A persistent Call and WhatsApp bar lifts Act from 0 to 2 on its own, and compressing the hero image usually moves Speed up a point. The total goes from 5 to 8 with a few days of work.
Scorecard checklist
- Pick your top three landing pages from analytics.
- Use a real phone on mobile data, ideally a mid-range one.
- Score Read, Tap, Speed, Act and Parity from 0 to 2 on each page.
- Take the lowest score per test and add them up.
- Write down the specific reason for every score below 2.
- Fix any 0 first, then the 1s on your highest-traffic page.
- Re-score after the changes and again each quarter.
Next step
Set aside an hour this week, pick up a phone and score your site honestly. The number you get is the most useful input to any conversation about your website, whether with us or with anyone else.
Message us on WhatsApp with your score and we will tell you which fix to make first.
Chat on WhatsApp →Sources and further reading
- Accessible tap targets · web.dev (Google)
- Understanding Core Web Vitals and Google search results · Google Search Central
- Mobile-first indexing best practices · Google Search Central
- PageSpeed Insights · Google
Frequently asked questions
How do I score my website for mobile?
Open your top three landing pages on a real phone over mobile data and score five tests from 0 to 2: can you read it, tap it, does it load quickly, can you act within a minute, and does it match the desktop content. Add the lowest score per test for a total out of 10.
What is a good mobile readiness score?
On the GBL Mobile Readiness Scorecard, 8 to 10 is mobile-ready. 5 to 7 means the site works but is losing enquiries and needs targeted fixes. 4 or below means the site is failing on phones and a redesign or rebuild should be considered.
Is a scorecard better than PageSpeed Insights?
They do different jobs. PageSpeed Insights measures loading and responsiveness against Google's thresholds. A scorecard checks what a customer experiences, including whether they can read, tap and get in touch. Use both: a site can pass one and fail the other.
How often should I re-score my mobile website?
Every quarter, and after any redesign, new plugin, template change or major content update. Mobile problems creep in through small changes, such as a new pop-up or a larger hero image, so a regular check catches them before they cost enquiries.
Written by

Global Bridge Labs (GBL) is a UK–Sri Lanka partner for social media, websites and BPO. Everything here comes from client delivery, not theory.




