Thanks to some recent advances in bundler technology, it’s possible to deploy your production code as ES2015 modules—with both static and dynamic imports—and get better performance than all non-module options currently available.
Reasons to keep optional code around typically boil down to understandability, whereas reasons to leave out optional code converge on performance. What code—here: what HTML code—is optional, however? This article gives an overview over everything optional other than extraneous whitespace.
This is a very clever idea via Arthur Corenzan. Rather than use the default YouTube embed, which adds a lot of resources to a page whether the user plays the video or not, use the little tiny placeholder webpage that is just an image you can click that is linked to the YouTube embed.
The concept behind AMP isn’t a problem. In fact, it’s fundamentally a good idea. Why shouldn’t mobile users have access to faster-loading, stripped-down web pages? The problem is that speed comes with a major catch.