Reason behind Gitlab's no-store cache policy

when I browse any repos on gitlab site, it takes same amount of time to view already viewed pages, as first time viewed pages. Even when you use browser’s back and forward button. (normally browser show you the cached version of the page when you use back/forward button, if there was no no-store response header). I wonder what was the rationale behind gitlab adding no-store, despite knowing that user experience is going to suffer. any views

So I am keen to know Gitlab’s rationale behind this