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

The <amp-iframe> component


The amp-iframe component allows you to add iframes to your AMP pages. In a well-attended talk at AMP Conf 2017, Sebastien Benz referred to iframes as the duct tape of AMP (watch: youtu.be/Em-tZ4WMMps [16:25]). This is an apt metaphor: like duct tape, iframes are incredibly useful, but just as duct tape is often not the prettiest solution, neither are iframes. Like duct tape, amp-iframe can stick things together, allowing us to combine features not supported in AMP. The prevailing advice, however, is that if there is a dedicated AMP component that implements the functionality you need, then you should use that instead of amp-iframe.

What about the risk to performance?

You might be wondering why third-party JavaScript or other non-validated content is permitted in AMP through iframes, with all the other restrictions in the name of performance. Malte Ubl, the AMP project lead, gives a couple of reasons why this is OK (support.google.com/partners/answer/7336293...