Using 1.6/0.8 3G speeds (with 300ms RTT) as the baseline, and specifically targeting a 3s SpeedIndex embarrasses most non-AMP experiences by virtue of the AMP c

Using 1.6/0.8 3G speeds (with 300ms RTT) as the baseline, and specifically targeting a 3s SpeedIndex embarrasses most non-AMP experiences by virtue of the AMP cache underlying the SERPs. These are the terms with which Google's marketing AMP specifically with its own tools for marketers. (To wit: https://testmysite.thinkwithgoogle.com/intl/en-us https://testmysite.thinkwithgoogle.com/intl/en-us) You can get damned close--and even exceed it if you're a minimalist--by throwing every bleeding-edge performance optimization under the sun at it, but nothing is going to stop marketers throwing Adobe's render-blocking VisitorAPI in the <head> to offset many of those optimizations, either. (Seriously, and you can't async it, either. Marketers get angry and Adobe doesn't support it.) The advantage of AMP dissipates rapidly as one tests in 4G and low-end cable speeds, however. At that point, hitting a 1s-2s SpeedIndex isn't terribly difficult if you're using front-end performance best practices, even with a framework bootstrapping itself to the DOM.