We are working and testing different tech stack and logic to optimize site perferomance as there were some complaints about it.

This should include some custom coded agressive caching logic.
From caching side public cache is dumb easy to setup, problems gets with logged in users.

We have structure like membership site and default logic for private cache based on IP is dumb as it gives short cache TTL and generates huge amount of caching files.

We are experimenting with custom coded membership logic to divide users into groups and make "private-public" caching based on membership tier so we could serve longer TTL, get far more cache hits with much less caching data as won't be per user rather per user cache group.