Of the 500 mobile homepages audited, here's what I was able to learn from the data:
❌ 395 or 79% of mobile homepages Failed Google PageSpeed Insights.
✔️ THIS: means 105 or 21% of mobile homepages Passed.
📱 IF: 164 sites or 32.80% had >66% mobile Chrome user traffic.
🚨 AND: 136 or 82.93% (of the 164 with >66%) had a Failed mobile homepage.
📲 THEN: Only 28 or 17.07% of them Passed, optimizing for their 2:1 mobile majority.
‼️ THAT: 136 or 82.93% of those with greater than 2:1 mobile/desktop traffic that Failed, are who could be providing the majority of their users a quicker initial experience.
BRANDS
CDJR
CHEVROLET
FORD
HONDA
HYUNDAI
KIA
MAZDA
NISSAN
SUBARU
TOYOTA
CITIES
Chicago, IL
Dallas/Fort Worth, TX
Los Angeles, CA
Miami, FL
New York, NY
To gauge just how closely the industry is keeping an eye on mobile homepage speeds. If your website is a football team, then think of your homepage as the quarterback. The quicker they release the ball off the snap, the more likely they are to avoid being sacked. If your homepage is like the quarterback, then a slow mobile homepage is only costing you lost customers in the form of frustrated shoppers bouncing from your site. The focus is identifying mobile homepages that have a need for speed.
Most of this is publicly accessible data via https://pagespeed.web.dev/, if witnessed here or previously me performing one of these reports, it was likely fetched using a variation of the 'Chrome UX Report API' and/or 'Pagespeed Insights API.' For more info on the testing process, see my previous post "Auto/Mobile Home CrUX Demo" or check out the more recent "What am I using Google APIs for?"