Drawbacks of SSR
- Slower Page Transitions: Transitioning between pages can be slower with SSR, especially if your site handles complex or heavy data. This is due to the double rendering process — once on the server and once on the client.
- Vulnerability: With a larger surface to attack, SSR sites can be harder to secure compared to CSR sites. Knowledge and diligence in security practices are essential to mitigate this issue.
- Complex Caching: Caching strategies tend to be more complicated with SSR, requiring more effort to configure effectively compared to CSR.
- Server Cost: High-performance SSR may necessitate more robust and costly server resources than CSR.
- Higher Latency: During peak traffic, SSR sites might experience higher latency, affecting the browsing experience. This issue is less prevalent in CSR, where latency, or ping rate, plays a smaller role in performance.
Is Server Side Rendering(SSR) always good ?
SSR is a technique used in web development where the HTML of a webpage is generated on the server rather than in the browser. This means when a user requests a webpage, the server prepares the HTML document by executing the necessary logic and sends it to the client’s browser, fully formed and ready to be rendered. This approach is different from CSR, where JavaScript runs in the browser to generate HTML content dynamically.
Table of Content
- How server-side rendering work?
- Benefits of SSR
- Drawbacks of SSR
- When to Use and When Not to Use SSR
- Hybrid Approach
Contact Us