Earlier this year at AMP Conf, we introduced the developer preview of <amp-script>. Now we are announcing the general availability of <amp-script>. It’s an AMP component that runs your own JavaScript in a separate Worker thread.

Today, we’re excited to announce our solution for arguably the biggest issue affecting Accelerated Mobile Pages (AMP): the inability to use real origin URLs when serving AMP-cached content.

Let’s talk about Accelerated Mobile Pages, or AMP for short. AMP is a Google pet project that purports to be “an open-source initiative aiming to make the web better for all”.

As mobile-first indexing nears, the need to optimize for mobile has never felt so pressing. Even in its current iteration, mobile search is incredibly important for advertisers and businesses of all sizes. Consider these statistics:

AMP has caused quite the stir from a philosophical perspective, but the technology hasn’t received as close of a look. A few weeks ago, Ferdy Christant wrote about the unfair advantage being given to AMP content through preloading. This got me wondering: how well does AMP really perform.

Update: Since October 2017, there is a partial solution to this developed and announced by Google. Learn more about it here.

DigitalOcean provides cloud products for every stage of your journey. Get started with $200 in free credit! The Accelerated Mobile Pages (AMP) Project is an initiative to improve the mobile web and enhance the distribution ecosystem.