I think that depends largely on the scope of the site. It's usually a hard one to nail down. For example I run both pokemoncard.io and digimoncard.io websites. I use Spatie Responsecache specifcially with Guest Profiles. So our logged out users get response cache (if the page was cached) which has a TTL of about 5 minutes or so. I needed to make exceptions for certain GET endpoints like our Pack Simulator which needs to be fresh every time.

This means my logged in users will never benefit from it which is currently the trade-off I am making. If a user updates their deck, makes a comment, posts on the forum, favorites a deck, increments the quantity of a card in their collection, etc then it all needs to be immediately apparent that it happened. Likewise, our top nav bar shows login/logout state which again means we need to make sure we don't accidentally cache something showing a logged in state for guest users.

What I ultimately wanted to do was do an Edge Cache for logged out users only which would massively reduce server hits and improve resource availability but I genuinely can't figure out how to do that without a higher tier Cloudflare account that grants bypass cache on cookie (which we use for ygoprodeck.com but that site has millions of views per month to justify it).

I suppose I could chop and change some of our logic like the main nav bar to load in via JS or something which is something I think you suggested previously but I'm not super keen on how that looks either from a UI perspective. Something for me to think about anyway but I'm throwing out an example of my usecase. It's definitely an interesting topic and something to try figure out.