The solution
By 2015, mobile news pages were heavy enough that speed itself had become a product problem. The obvious fix was better site engineering, but publishers varied wildly in tooling and incentives.
Google's AMP made speed portable. Publishers created an AMP version under a stricter HTML and JavaScript regime, while Google surfaced AMP pages in mobile Top Stories and served them quickly from cache.
The format's power came from distribution. Engadget reported the 2016 rollout with claims that AMP pages loaded up to four times faster and used up to ten times less data, and Wired noted that AMP was required for the Top Stories carousel at launch.
That made AMP both a standard and a bargain: accept a narrower page format and gain a fast lane in mobile news discovery.
What it achieved
Make performance a format gate
Why it worked
It converted a fuzzy performance goal into a concrete validation target.
It solved adoption with traffic incentives rather than persuasion alone.
It let publishers keep the open web URL model while getting app-like loading speed.
What can be applied
If a standard asks people to give something up, attach it to a channel they already need.
Aftermath
AMP became common across news sites, then lost its exclusive gate. Search Engine Land reported that Google would stop requiring AMP for mobile Top Stories in 2021, shifting the lesson from AMP itself to the power of making performance measurable and distributable.
FOLLOW THE EVIDENCE
The sources
- Google brings fast-loading articles to your phone engadget.com
- Google Will Now Favor Pages That Use Its Fast-Loading Tech wired.com
- AMP won't be required for Google's Top Stories section searchengineland.com