(Accelerated Mobile Pages). From February 24th onward, Google search results began to include links to mobile-page versions that were built with this open-source project. When Google begins openly backing a technology, you know that it’s going to be a big thing, but what exactly is AMP? AMP is all about the mobile user experience. Specifically, the initiative is meant to make mobile pages faster than ever before, which is a surefire way to improve the UX. Ideally, AMP proponents want to be able to create mobile content only once — and then already have it load immediately everywhere else. As with all new initiatives, we need to separate the truth from the hype…
Making your sites faster
Since Google’s public push in favor of AMP last year, many high-profile companies who publish on the web have also begun to back AMP. Some of these names include the BBC, the Wall Street Journal, the Guardian, Twitter, Pinterest, the New York Times (itself in the middle of an ad-wars controversy), and Buzzfeed. Naturally, they want to be on the bandwagon because they’re saying to themselves that any initiative that Google supports is bound to impact our SEO rankings. However, is it really worth it for these companies to support AMP at this time? Does AMP deliver on its promise to make your site faster?[pullquote]if you already understand UX…AMP may not prove to make such a big difference after all[/pullquote] To begin to answer that question, we have to put it in context: If you’re comparing your site to a media-rich site that only has average optimization, then it’s likely. Yet if you’re comparing your site to one featuring minimal design and good optimization, then the jury’s still out. In other words, it’s case-sensitive. If you’ve been one of those early AMP fans who’s already bought into its apparent speed, consider the following: AMP isn’t a new type of technology. Why, even Google admits that AMP was created out of already existing Internet technologies, for the purpose of creating lightweight pages. So, no, there isn’t anything exactly revolutionary about it. Understanding this will help in putting into proper perspective the speed hype surrounding AMP. So if you already understand UX intimately and know how to integrate the latest performance enhancements into your site design and development, then AMP may not prove to make such a big difference after all.
What exactly is AMP?
This open-source project was born from discussions between tech companies and publishers about the need to better mobile UX for everyone involved with content: consumers, publishers, creators and users. AMP, it’s important to point out, isn’t a radically new kind of HTML. In fact, as the Project explains, AMP are like other HTML pages, the only difference being a limited set of permissible, technical functionality that’s governed and defined by the AMP spec. AMP will load in any app web view or modern browser, just like ordinary HTML pages, but speed’s a priority due to different, architectural approaches. AMP also promises greater speed because of the reduced amount of code. For example:- You have less than 50 kb of CSS
- You don’t need your own JavaScript (there’s no JS-powered tabs, alerts, tooltips or modals)
- You don’t have code for various ad providers and analytics services
- Lazy loading
- Preconnecting
- Prefetching
- Prerendering
Only faster in some cases
The truth of the matter is that AMP will only make your site faster in some, specific situations. It all depends on the site’s tech considerations, but also the needs of the business that the site supports.[pullquote]not using AMP doesn’t mean that you can’t design and tweak your site for speed[/pullquote] Here’s when AMP can make your site faster:
- If your site is so media-rich that it will automatically benefit from the optimized loading processes
- If you want AMP to be in charge of optimizing your site’s speed and performance instead of you handling it yourself