[Master Feature] Improve performance on AMPHTML ads when served to non-AMP pages

[jasti]

@lannka and @keithwrightbos to breakdown to tasks

• Reduce the size of the ads runtime

[keithwrightbos]

This is complete. AMPHTML ads on non-AMP pages served via GPT are now validated and optimized to include full version paths for AMP scripts, server side rendering with inline CSS, and tag injection within amp-img and amp-pixel elements.

[jasti]

In most cases AMPHTML ads are already more performant than non-AMP pages. This is certainly the case when compared to HTML5 creatives. However, when compared to simply image creatives, the AMPHTML variant is slower because it needs to download entire runtime to render the ad. Optimize the AMPHTML ad in a way that it's always better than a non-AMPHTML ad.

Performance in this case means 'optimizing to get the creative to render as quickly as possible' which translates to increased viewability, higher click through rate of the ad.

[ampprojectbot]

This issue hasn't been updated in awhile. @keithwrightbos Do you have any updates?

[jeffkaufman]

when compared to simply image creatives, the AMPHTML variant is slower because it needs to download entire runtime to render the ad

Server-side rendering can convert the AMPHTML variant to HTML, such that the browser can display the image immediately, without waiting for the runtime to load. This is what Doubleclick has deployed.

I know @lannka has other plans for improving the efficiency of Inabox, like making a separate and much smaller runtime, but I think this is tracked elsewhere?

[ampprojectbot]

This issue hasn't been updated in awhile. @keithwrightbos Do you have any updates?

[lannka]

let's track inabox lite work here: #22867