<5% of hero images are mobile-ready. After 20 years of smartphones. The iPhone l
By Oliver Bradley · April 17, 2026 · Curated by George's Blog
<5% of hero images are mobile-ready.
After 20 years of smartphones.
The iPhone launched in 2007. We've had two decades to figure out how to design for mobile at scale.
And yet:
❌ Less than 5% of hero images pass the GS1 definition of mobile-ready (DCG & FirstMovr have measured this)
❌ Less than 1% of PDPs are ready for agentic commerce. (Shoptalk 2026)
Brands are chasing Rufus and Sparky while 95% of their hero images can't even be read on a phone.
Over 75% of online shopping happens on mobile right now.
You'd be lucky to get 7.5% of the total online shopping population using Agentic AI to shop right now.
So why is everyone obsessing over agentic readiness when mobile readiness is still broken?
I know we need to optimise for Agentic, but the vast majority haven't realised they failed to optimise for mobile. And it's fixing ONE IMAGE.
=========================================
WHAT MOBILE-READY ACTUALLY MEANS and YOU CAN TEST IT
=========================================
According to GS1, a mobile-ready hero image must:
✅ Pass APCA contrast (Lc > 45)
✅ Pass the University of Cambridge Clarity test
If your hero fails either, it's not mobile-ready.
And if it's not mobile-ready, shoppers on mobile are encountering heavy VISUAL FRICTION on your heroes as they aren't designed for mobile.
Fix mobile first. Agentic matters sure but get your heroes fixed.
Rufus AI...uses heroes. Sparky...uses heroes.
But do your thumbnails pop, and stop the online shopper on their most preferred device for grocery shopping?
DM me if you want to test your heroes with RHINO AI.
We'll test your heroes for you.