Accelerated Mobile Pages & New Relic Browser

In early 2016, Google released a new technology called Accelerated Mobile Pages, or AMP. Aimed primarily at content publishers, AMP seeks to speed up delivery of content to mobile devices. The spec does this by creating a duplicate page, formatting it with AMP HTML, optimizing it in other ways such as blocking 1st & 3rd party Javascript, then caching and serving from a CDN. The result is a page that is served nearly instantly, from the users perspective.

The above means that New Relic JavaScript can’t live on an AMP page. Of course the good news is that our language agents and JavaScript were built to handle this situation. With growing popularity of AMP in the last month, we’ve created a page in our documentation that provides information on how to ensure that your AMP pages pass validation with Google without loosing any functionality on our other pages. This essentially means making an API call to exclude New Relic when the AMP page is created from the original content, which will continue to contain New Relic JavaScript.

As AMP continues to mature and gain adoption, we’ll ensure that New Relic customers continue to offer the best experience we can. In the meantime, keep monitoring your original content with New Relic, and exclude it from your AMP pages, as the Google spec requires.

1 Like