Google says it is taking the lessons it has learned from AMP and is applying them to web standards that could allow instant loading for non-AMP web content
Context & Ripple Effects
Google built AMP in 2015 as a constrained format — restricted JavaScript, banned tags like iframes — and seeded it with early adopters including The Guardian, Washington Post, and Vox via an open-source GitHub release. It then used its own distribution lever: starting in 2016, mobile search links began routing users to the AMP version of a page instead of traditional HTML when one was available.
By mid-2017 Google counted 2 billion AMP pages across 900K domains loading twice as fast. The new announcement flips the logic: rather than pulling publishers into a separate format, Google says it will push what AMP learned into web standards themselves, so ordinary non-AMP pages can load instantly too.
First-order effects
- Publishers who adopted AMP largely to keep instant-loading treatment in Google's mobile search results gain a path to drop the duplicate AMP versions of their pages without losing the speed benefit.
Second-order effects
- Browser vendors and standards bodies face pressure to implement whatever performance mechanisms Google proposes, since the value now depends on broad platform adoption rather than Google alone serving cached AMP copies.
Third-order effects
- If the pattern holds, page speed stops being a Google-controlled format advantage and becomes a baseline capability of the open web platform — shifting leverage over mobile distribution back from a proprietary cache toward standard HTML.
The trend: Web performance is migrating from Google's parallel AMP format into open web standards, dissolving the trade-off between speed and format control that defined AMP's launch.