/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Google says there are 2B pages and 900K domains using AMP; pages now load twice as fast

Improving speed and user experience … Emil Protalinski / VentureBeat : AMP pages from Google Search now load twice as fast Tweets: Chris Ciaccia / @chris_ciaccia : AMP much better than FB Instant articles http://twitter.com/... See also Mediagazer

TechCrunch Ingrid Lunden

Context & Ripple Effects

AMP launched in late 2015 as a stripped-down HTML variant — restricting JavaScript and banning tags like iframes in exchange for near-instant loading — and by mid-2016 Google committed to routing mobile search results to the AMP version when one exists, making adoption a traffic question for publishers rather than a technical curiosity.

Today's numbers — 2 billion pages across 900,000 domains, with Search-served AMP pages now loading twice as fast — mark the point where the format has become default infrastructure for news publishers. The open questions are whether the speed dividend actually accrues to publishers, and how much of the mobile web ends up served from Google's cache.

First-order effects

  • Publishers weighing AMP adoption get a stronger pitch from Google — doubled load speed plus preferential placement in mobile Search via the 2016 routing change — while giving up control over JavaScript, iframes, and their own page rendering.

Second-order effects

  • Facebook's Instant Articles becomes the direct rival format competing for the same fast-loading news inventory, with publishers forced to pick which platform's constraints to accept — or maintain both.
  • Ad-tech and analytics vendors face pressure to rebuild their tools inside AMP's restricted runtime, since standard third-party scripts are exactly what the format bans.

Third-order effects

  • If Google's cache-and-constrain model holds, the mobile web splits into two tiers — AMP pages that get the fast lane and everything else — concentrating route share over who reaches readers in the hands of the search platform rather than the publisher.
  • Google's own stated plan to fold AMP's lessons into open web standards points toward the constraints eventually dissolving into the platform itself — though whether publishers' traffic gains survive that transition is what later measurement would test.

The trend: Mobile publishing is shifting toward platform-defined performance formats, where the operator of the dominant distribution channel sets the technical terms of reach.