Why would you want that instead of AJAX-y functionality? Page reloads increases wait times, and depending on use case, drastically increases page size.
>Page reloads increases wait times, and depending on use case, drastically increases page size.
Considering the sizes of the javascript libraries loaded by all of the websites, I find it unlikely that the page size for a static page will be larger.
The average size of a single page is larger than a doom install now. That's not because of orders of magnitude more of HTML. It's because of the 15 different tracking JS libs, analytics libs, effects libs, etc that are piled into every site.
Full page reloads were a big deal when most people were on dial-up connections.
With proper caching and today's connectivity it's far less of an issue.
AJAX-y still is nicer and definitely has its place but at least speaking for myself if I'm reading a blog or a news site I'd prefer a fast static page rather than a lot of gratuitious ajax animations and transitions.
The big difficulty these days is mobile. When I'm traveling, I can download a simple HTML page pretty quickly, but every request is a crapshoot. If I need more than a few small requests to use your site, I'm likely not getting it depending on where I am.
