Tasked with researching caching the html response on our nuxt 2 app. The site relies heavily on the store. The store is persisted through nuxt.init in the store/index.js by checking cookies and re-populating the store. It is an SSR ecommerce app. the shopping cart is in the store. auth information is in the store. certain data in the store is used to provide correct UI. From what I can gather, caching pages will be difficult due to the data in the window when the page is rendered server side containing store info. if i could know for sure the user is in a default, first visit state maybe i could cache in those instances but it seems risky and complext to implement. The goal is to improve the time to first byte data, which we believe consists mostly of nuxt rendering the page on the server. if i move the store population to nuxts onmount(), the page would noticeably change drastically as the store is set, and that is a poor user experience. It also seems like i am at odds with litespeed which proactively disables caching if any cookie at all is present.