Strengthening the AMP ecosystem

Accelerated Mobile Page ( AMP) is a project from Google and Twitter designed to make really fast mobile pages. At its essence, it's basically a stripped-down form of HTML, a diet HTML if you will.  fundamentally, it's an HTML page designed to be super lightweight and critically designs really fast loading. So Google, Twitter, a bunch of other companies have rolled this out — kind of in response to projects like the Facebook Instant Articles project from Facebook and Apple News and so forth. This is designed to be the open response. So it's open source, and there are all kinds of elements of openness to the project.
 
Everyone knows that Google is a giving high priority for Mobile-friendly pages. While everyone was busy in making mobile friendly pages, Google comes up with the great open source initiative called Accelerated Mobile Pages (AMP). There are two benefits behind this important initiative is Quick Read Carousel showing up in search engine results and higher ranking factor. Browsing on mobile while moving will mean that your internet speed will be not always fast. So it’s the best option optimize the mobile browsing experience of for all users. AMP pages load 4x times faster and use 8x fewer data when compared to regular web pages.

A strong network of AMP contributors and collaborators has been critical to achieving the project’s mission of building a user-first web. At Google’s I/O developer conference this week, members of the AMP team are sharing recent ways the AMP community has come together to improve key elements of the AMP ecosystem.
 

Difference Between AMP and Non-AMP Mobile Browsing?

1.    Google AMP forces the user to use a streamlined version of CSS.

2.    Google AMP does not allow manually entered javascript; it has its Javascript library which forces your images to lazy load.

3.    Javascript is not allowed at all. (But there are some loopholes that we can create Share buttons and to display ads)

 
Site owners and users have equal benefits. It’s much faster and more streamlined for searchers, especially on mobile devices that tend to be a little bit slower connection-wise. AMP’s evolution has made it a viable solution to build entire websites. 
 
Lastly, support for AMP in the CMS ecosystem is critical to ensuring it’s easy to author content on the web. WordPress is one of the most popular tools for authoring web content, so Automattic, XWP, and Google are working together to advance the WordPress AMP plug-in. The recently launched 0.7 version includes native AMP support, allowing the creation of entire sites with AMP with the standard WordPress content creation workflow.
 
Google also shared that new platforms and websites have joined the AMP ecosystem. There are already over 2 billion AMP pages and 900,000 domains with AMP on the web. Even within the search sphere, Google isn’t the only one supporting AMP: Bing, Baidu, Sogou, and Yahoo Japan are also all on board.
 
China’s largest social network, Tencent Qzone, and the country’s third-largest, Weibo, are adopting AMP pages. Tumblr says it is publishing 340 million blogs across 500,000 domains in AMP, starting this week. Twitter is linking to AMP pages from its new mobile web app and will be launching AMP support in its Android and iOS apps. Zalando is getting in on the action as well, implementing AMP for its 250,000 product pages, and eBay plans to use AMP across all its product pages. In summary, Google has managed to keep AMP momentum going.