Google Announces Accelerated Mobile Pages

Google announced the Accelerated Mobile Pages (AMP) project on October 7, 2015 and began rolling out AMP results in Google Search in February 2016. AMP was conceived as a response to the mobile web’s performance crisis: news and publishing sites serving rich HTML pages with large JavaScript bundles, advertisement scripts, and tracking pixels were taking 8-22 seconds to load on 3G connections — slow enough that users frequently abandoned pages before they finished loading, and that competing closed platforms (Facebook Instant Articles, announced May 2015; Apple News, announced June 2015) offered significantly faster reading experiences by serving content inside native apps rather than the mobile browser. AMP’s technical approach was a restricted HTML subset — AMP HTML — that banned arbitrary JavaScript entirely (replacing it with an AMP component library), required explicit size declarations on all external resources (images, iframes, ads) to prevent layout shifts as content loaded, and mandated asynchronous resource loading to ensure the page’s content was never blocked by an external script or stylesheet. AMP JS was the library that managed asynchronous resource loading, extension components (<amp-img>, <amp-video>, <amp-ad>, <amp-analytics>), and rendering optimization. The AMP specification was open-sourced on GitHub and positioned as a community project rather than a Google-proprietary format, though Google remained the primary contributor.

The performance gains AMP promised came substantially from the AMP Cache: Google’s CDN that validated AMP pages, cached them on Google’s infrastructure, and served them from google.com/amp/… URLs when users tapped search results on mobile. Google pre-fetched AMP Cache pages in search results before the user even tapped — loading the page in the background while it was visible on the search results screen — making the tap-to-content time feel near-instantaneous. AMP pages displayed with a lightning bolt ⚡ icon in Google Search results and were placed in a horizontally scrollable “Top Stories” carousel at the top of search results for news queries, giving participating publishers significantly greater visibility. Major publishers adopted AMP rapidly: the Washington Post, BBC, BuzzFeed, The Guardian, and hundreds of other news organizations published AMP versions of their articles within the first months. Load time improvements were genuinely measured: Google reported 85 percent faster loading and 35 percent longer engagement on AMP pages compared to publishers’ non-AMP pages in independent studies.

AMP’s controversy grew in proportion to its adoption. The most visible problem was URL display: when users shared or bookmarked an AMP page, the URL shown was a google.com/amp/… address rather than the publisher’s own domain — breaking publisher branding, interfering with analytics that relied on referrer tracking, and complicating link sharing in ways that damaged direct traffic attribution. The “Top Stories” carousel’s AMP requirement (until September 2021, when Google began accepting non-AMP pages in Top Stories) meant publishers faced a choice between building and maintaining an entirely separate AMP version of their website or losing eligibility for the highest-visibility mobile search placement — a dynamic critics described as Google leveraging its search monopoly to control web publishing standards. The governance concern — that one company controlled both the specification and the primary distribution mechanism — led to AMP being restructured under the OpenJS Foundation’s governance in October 2019, though Google remained the dominant contributor. When Google launched Core Web Vitals (June 2021) as a set of page experience signals (Largest Contentful Paint, First Input Delay, Cumulative Layout Shift) that would factor into search ranking, it simultaneously announced that AMP would no longer be required for Top Stories eligibility — publishers could achieve the same search visibility through good performance on standard HTML pages. This effectively ended AMP’s period of Google Search preferential treatment, and AMP adoption began declining as publishers who had only implemented it for search benefits had less incentive to maintain two website versions. For web performance engineering, AMP’s period of influence had demonstrated that constrained HTML subsets with strict resource budgets could radically improve load times, a lesson that informed subsequent web performance standards even after AMP itself receded.