Yesterday I said we should stop saying "Mobile-Optimised" and start saying "Mobi
By Oliver Bradley · May 20, 2026 · Curated by George's Blog
Yesterday I said we should stop saying "Mobile-Optimised" and start saying "Mobile-Readable."
Here's why.
This is Go Ahead. A well-known snack brand. Much loved in our household. Their hero image looks fine on a desktop.
But I tested it with RHINO AI from Neem.
The problem was that this hero wasn't tested for glance-readability.
===========================
It is not a "Mobile-Readable" hero image.
===========================
"CHERRY" is too small and fails "Text Size CLARITY" = VARIANT FAIL
"54 Kcals" claim fails CONTRAST = "CLAIM FAIL" (Claims aren't part of 4Ws)
Mobile-readable means:
✅ APCA contrast passes for all 4Ws
✅ Text size Cambridge Visual Clarity passes for all 4Ws
So actually only ONE 4W fails which is a pretty decent effort.
They probably didn't know until now and I'm a GO AHEAD fan so if you are reading this it's not to shame your previous effort.
AI has now made it easier to test your heroes. The fix isn't complicated. Test before you publish.
To our CPG industry here's my ask...
PLEASE Don't call it "mobile-optimised" if you haven't tested it,
Call it what it is: mobile-readable. Or not.
Team "GO AHEAD", we'd like to offer to test 50 of your heroes for free.
You've been kind to my household snacking needs.