Content caching can decrease the time it takes to load a web page.
But it doesn’t work if the page contains personal content because one user may receive another user’s personal content which is a breach of privacy and just doesn’t work.
This can lead to the use of AJAX to load in the personalised content as a separate request which has a number of drawbacks.
Before explaining them, I‘ll first define what I mean by personalised content.
# Personalised content
Personalised content is content that is specific to a user.
At the most basic level, a “sign out” link
See original post