One of pain parts with SSR applications when depending on external REST APIs, is that we fetch and hydrate payload data. For instance by checking landing page's html source, we have ~34250 minified chars of json data which is barely used in page this causes network latency, js parsing overhead (CPU) and memory usage.
Action points:
- Use a serverMiddleware as BFF layer to reduce payload for landing page
- Investigate actual perf improvements
- Investigate possibility of creating a nuxt tool to analyze this for users about how much of hydrated data is accessed (via a proxy maybe)
One of pain parts with SSR applications when depending on external REST APIs, is that we fetch and hydrate payload data. For instance by checking landing page's html source, we have ~34250 minified chars of json data which is barely used in page this causes network latency, js parsing overhead (CPU) and memory usage.
Action points: