WordPress.com sites now automatically support Google's AMP to speed up mobile page loading; self-hosted WordPress sites can enable AMP with a plugin
WordPress Sites Now Support Google's AMP To Make Mobile Pages Load Much Faster — Google has some big plans when it comes to making the web faster on your mobile phone.
Context & Ripple Effects
Google launched Accelerated Mobile Pages five months ago with Twitter, Pinterest, Adobe and LinkedIn as partners, opening the code on GitHub while The Guardian, Washington Post and Vox ran early implementations. The catch was cost of adoption: the format imposes real constraints, restricting JavaScript and banning tags like iframes in exchange for speed.
WordPress.com flipping AMP on automatically removes the last practical barrier for the long tail — millions of hosted sites get fast pages with zero developer work, while self-hosted WordPress operators get a plugin. Distribution at this scale turns AMP from an experiment among large publishers into default infrastructure for the open web.
First-order effects
- WordPress.com publishers instantly become eligible for Google's fast-loading mobile treatment without touching code, and self-hosted site owners can opt in through a plugin rather than custom engineering.
Second-order effects
- Other CMS and hosting platforms now face pressure to ship equivalent one-click AMP support or lose ground on mobile search visibility.
- Publishers who enable it trade some control for speed: pages render from Google's constrained format, a trade-off that later fuels accusations that AMP siphons publisher traffic into Google-hosted caches.
Third-order effects
- If adoption keeps climbing — Google would later report 2 billion AMP pages across 900K domains — the mobile web splits into two tiers: standard pages and platform-constrained fast pages, shifting power over how content renders from publishers toward whoever controls the distribution layer.
The trend: The mobile web is consolidating around Google-defined performance standards as publishing platforms bake them in by default, trading page autonomy for speed and reach.