I should have clarified: the assets are indeed cached well – what I’m talking about is the HTML document (first request).
Most of the full pages that you can see are dynamic and should not be aggressively cached. It would be possible I guess to have the kind of ETag caching where it checks every page load if there are no new or edited posts. I’m not sure why the team decided not to do this.
Yes this is essentially what I’m talking about, but I don’t think ETag’s are generated by hand like that – they can be based off the raw html that is being served and can tell the client, “hey this is exactly what you saw before, just use that”