AMP: Does it really make your site faster?
Accelerated mobile pages (AMP) deliver a fast user experience for mobile devices by placing restrictions on the AMP markup and its ability to run code. Without code, how can we gather analytics or validate that our AMP pages are fast? Nic Jansma and Nigel Heron demonstrate how to gather RUM for AMP.
| Talk Title | AMP: Does it really make your site faster? |
| Speakers | |
| Conference | Velocity |
| Conf Tag | Build resilient systems at scale |
| Location | Amsterdam, The Netherlands |
| Date | November 7-9, 2016 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
The goal of the Accelerated Mobile Pages (AMP) project is to give publishers a way to distribute their content in a highly performant way on mobile devices, resulting in happier visitors. Publishers are beginning to invest in AMP support now that AMP pages are becoming prioritized in search results. With the lower markup complexity of AMP pages, you can also reduce your development and infrastructure costs. As with all magical solutions, AMP has its downsides. To achieve some of its goals, AMP pages strictly limit what components can be on the page, and a major restriction is that JavaScript is not allowed. This brings up a few serious concerns: Nic Jansma and Nigel Heron cover the benefits, challenges, and alternatives to AMP. Along the way, they discuss why your old performance measuring techniques won’t work, how new AMP features attempt to bridge the monitoring gap, how the AMP project is being improved to help measure more real-user performance characteristics of AMP pages, and how the boomerang team is working with the AMP project to get there.
