How server-side rendering work?

Server-side rendering is the predominant method used to present information on a display. It involves the server transforming HTML documents into data that the browser can interpret.

Every time you access a website, your browser sends a request to the server hosting the website’s content. The duration of this request is brief, typically a few milliseconds, but it can vary based on several factors:

  • Your internet connection speed
  • The geographical location of the server
  • The number of people accessing the site simultaneously
  • The level of optimization of the website, among others

After processing the request, the browser receives the fully rendered HTML and displays it on your screen. Should you navigate to a different page within the same website, your browser will submit a new request for the specific content. This process repeats for every new page you visit that isn’t already stored in the browser’s cache.

Regardless of whether the new page has only minor differences from the current one, the browser will request the entire page and render it anew.

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

Similar Reads

How server-side rendering work?

Server-side rendering is the predominant method used to present information on a display. It involves the server transforming HTML documents into data that the browser can interpret....

Benefits of SSR

Faster Initial Page Load: SSR can significantly improve the time to first byte (TTFB), providing content to users more quickly. This can be particularly advantageous for SEO and for users with slow internet connections. SEO Optimization: Search engines can more easily crawl and index SSR pages, as the content is already compiled into HTML upon their request. Social Media Sharing: When sharing links on social media, SSR ensures that metadata (like images and descriptions) is properly loaded and displayed in the preview, enhancing engagement....

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....

When to Use and When Not to Use SSR ?

When to Use SSR:...

Hybrid Approach

How It Works...

Contact Us