There are some interesting trade-offs in this. There is more JS being processed, but that JS is smartly split up, bundled and takes care of loading just the co

There are some interesting trade-offs in this. There is more JS being processed, but that JS is smartly split up, bundled and takes care of loading just the content you need on subsequent browsing. So the gains are: - less data sent over the wire overall - faster page loads overall initially and especially on subsequent loads. - on subsequent loads only parts of the DOM are being rendered, not the whole thing so in some cases it might save you processing power - no round trips to a DB and template engine, this is mostly a pro for the provider of the content - some sites with this pattern enable you to download the whole thing as a PWA, so you can look at it offline with a single download.