Articles published with Accelerated Mobile Pages (AMP) load four times faster than standard mobile pages with a 35% improvement in engagement time, according to new research from Chartbeat.
Facebook Instant Articles (FIA), a key competitor to Google’s AMP product, load faster than AMP. But publishers see three times as many AMP articles viewed per day than FIA articles.
This comes hot on the heels of a stream of encouraging news on AMP from the Google I/O keynotes, presented by VP product management Rahul Roy-Chowdhury and Malte Ubl, creator and tech lead of the AMP Project. These included:
- There are now 2 billion AMP pages from over 900,000 domains, as of May 2017. A year ago there were 125 million AMP pages.
- An average AMP page loads in less than a second and uses ten times less data than a normal mobile page.
- AMP supporters and partners include Twitter, Tumblr, Qzone, Weibo, Pinterest, LinkedIn, Bing, Feedly, Nuzzle.
- AliExpress reduced load times by 36% with AMP, helping to increase orders by 10.5% and conversion rates by 27%.
Meanwhile, in late May 2017, Facebook announced an extension to its Software Development Kit (SDK) so that articles produced for FIA will also be publishable as AMP articles, and soon also as Apple News. This is in response to publisher frustration at having to produce content in different formats for different platforms.
Facebook’s move could also be a reaction to a number of publishers reportedly dropping Facebook Instant Articles, and a recognition the FIA is losing ground to AMP.
A recap: What is AMP?
AMP is special type of slim-line mobile webpage, which is an open source project, led, or controlled (depending on your viewpoint), by Google. AMP web pages are faster because:
- AMP is not part of the publisher’s main website (less baggage to download).
- The content is static (less interactive baggage to stall download).
- The articles are pre-cached on servers around the world, by Google or its AMP partners, so they are closer to the user (faster to download).
Any web page could be – and should be – speeded up in a similar way, by reducing page bloat, and using caching via a content delivery network. But the advantage of AMP is Google will only cache AMP pages and Google promotes AMP pages in mobile search above non-AMP pages.
As demonstrated by the following screenshots, of a Google search for “Trump” captured concurrently on a tablet and smartphone, using the tool mobilizer, AMP news stories dominate mobile search results for topical terms. Not just in the picture-led carousel of news, but throughout search results. AMP doesn’t feature at all in tablet results, which is baffling.
What the difference between AMP, Facebook Instant Articles, and Apple News articles?
Facebook Instant Articles and Apple News are news articles from third-party publishers that appear in the newsfeed on the Facebook app and within the Apple News app, respectively. They are tightly controlled by Facebook and Apple and only available to users of those apps. They are also not discoverable through web search or other third party sites or apps.
While these platforms present additional distribution channels for publishers, there is a double drawback to using them: the potential for losing out on direct traffic to their own sites and apps (where they potentially control all the ad revenue), and also the need to prepare articles in three additional formats.
Chartbeat’s research is particularly interesting as it provides an independent assessment of AMP and a comparison with FIA. There’s no inclusion of Apple News in the research, which is unfortunate as little is known about the platform except that it has 70 million users, according to Recode.
Chartbeat compared 360 sites that use both AMP and FIA, from its 50,000 media sites that use its analytics tools. So how did AMP stack up in the race against Facebook?
Speed and engagement
Let’s start with speed and engagement.
- The research found the average mobile web article took 5.3 seconds to load, but AMP took 1.4 seconds. That’s not as quick as Google’s claim of under a second, but it is a four-fold improvement.
- FIA loaded in a fraction of that time at 0.001 seconds, on most occasions too fast for Chartbeat to measure.
- Comparing the read time of visitors coming from search, Chartbeat found readers engage with AMP articles for an average of 48 seconds v 36 seconds for normal mobile articles i.e. 35% longer.
- There were no comparable engagement stats for FIA.
Considering AMP’s focus on speed, this comparison with FIA is embarrassing. However, Google is already working on speeding up AMP.
In his Google I/O keynote, Malte Ubl announced a plan to make AMP twice as fast to deliver “first contentful paint” – a technical term referring to the first ‘interesting bit’ of a webpage that the browser loads.
In practice, this will make it twice as quick to access the important part of a document, e.g. the text in an article, when clicked through from search.
On a daily basis, publishers see three times as many AMP articles viewed as FIA articles, according to Chartbeat. The report authors concluded from these results that content has a longer lifespan on AMP, or receives traffic for more days from AMP, than from Facebook Instant Articles.
Article volume matters to publishers. Especially when they have to reproduce content for different platforms, as well as, and in competition with, their own sites and apps.
As noted above, Facebook has opened up its SDK so articles produced for FIA would also be AMP and Apple News ready.
Similarly, if AMP volume continues to plateau for these publishers as Chartbeat suggests it has since the beginning of the year, publishers could become restless.
AMP vs mobile web
The biggest competitor to AMP probably isn’t FIA or Apple News; it’s the plain old mobile web.
Chartbeat’s research shows that publishers that use AMP and FIA have seen them steadily make more of an impact on mobile traffic. But today AMP is 16% of all mobile traffic for AMP publishers, and FIA is 14.8% of all mobile traffic for FIA publishers. While this is still significant, the majority of mobile traffic is not made up of either.
Not everyone is happy with AMP
There has been a growing number of voices of dissent to AMP. A lot of this sentiment is summed up in this provocative Register article, calling on Google to “Kill AMP before it kills the web”.
It’s clear from the Google I/O keynote that AMP publishers have also raised issues. Elena Legeros highlighted and addressed four key challenges:
- All AMP pages look the same. Response: Google is releasing more templates through AMP start.
- It’s hard to measure/track visits to AMP pages. Response: Google Analytics is working with third party analytics companies to improve this.
- Not everyone likes AMP URLs in Google Search. Response: Google recognizes that it is frustrating. Will work with partners to display the original article URL.
- AMP pages do not monetize well through ads. Response: Google disagrees.
Andy Favell is Search Engine Watch’s columnist on mobile. He is a London-based freelance mobile/digital consultant, journalist and web editor. Contact him via LinkedIn or Twitter at Andy_Favell.