Book Image

AMP: Building Accelerated Mobile Pages

By : Ruadhan O'Donoghue
Book Image

AMP: Building Accelerated Mobile Pages

By: Ruadhan O'Donoghue

Overview of this book

Google introduced the Accelerated Mobile Pages (AMP) project to give mobile users lightning-fast response times when accessing web pages on mobile devices. AMP delivers great user experiences by providing a framework for optimizing web pages that otherwise would take much longer to load on a mobile platform. This book shows how to solve page performance issues using the mobile web technologies available today. You will learn how to build instant-loading web pages, and have them featured more prominently on Google searches. If you want your website to succeed on mobile, if you care about SEO, and if you want to stay competitive, then this book is for you! You will go on a mobile web development journey that demonstrates with concrete examples how to build lightning-fast pages that will keep your visitors on-site and happy. This journey begins by showing how to build a simple blog article-style web page using AMP. As new concepts are introduced this page is gradually refined until you will have the skills and confidence to build a variety of rich and interactive mobile web pages. These will include e-commerce product pages, interactive forms and menus, maps and commenting systems, and even Progressive Web Apps.
Table of Contents (24 chapters)
Title Page
Credits
About the Author
Acknowledgements
About the Reviewer
www.Packtpub.com
Customer Feedback
Preface
14
Actions and Events
16
amp-bind Permitted Attribute Bindings

Serving AMP pages to all mobile visitors


If you've set up your AMP pages as described in Chapter 1, Ride the Lightning with AMP, that is, with a <link rel="amphtml" ...> tag in your non-AMP pages pointing to your AMP pages, then unless you specifically set something up, the only way to get to your AMP pages is by clicking through a Google search result, or perhaps clicking on a Twitter or LinkedIn link. The point is, you're reliant on third-party services to decide which version of your page will be served to any particular visitor. But what if the user visits your website directly on a mobile device? They will still get your non-AMP, desktop page.

Since you've gone to the trouble of creating an AMP page that's optimized for mobile, wouldn't it be better to get as much value as possible from your AMP investment and serve it to all your mobile visitors, whether Google sent them or not?

To do this, you need some way to determine which visitors are mobile and which are not. This is essentially...