About Server-Side Rendering and its Pitfalls
Using static SSR rendering means that when a page is rendered, the rendered HTML is cached on the server. The pitfall here is that with server-side rendering, every time a new user interaction takes place, the server generates a new page. Once this page is generated, it has to be returned to the user. This entire repeat process can cause a dramatic increase in the loading time that is not quite desirable. Server-side rendering is used by websites that sport a very simple UI and have only a few pages.
In SSR, aka Server-side rendering, HTML is sent to the browser and this HTML contains a description about the page. With the content being already available, the only thing that remains to be downloaded is the CSS. When a user clicks a page’s link, a request is sent to the server by the browser and the process is accomplished by the server. This process is a burden on the server and its bandwidth. With its frequent server requests and the slow page rendering, server-side rendering is also replete with full-page reloads and the site interactions are also not rich.
- With the server-side rendering approach, search engines are able to crawl pages and render the first page and end up mirroring the remaining ones. This mirroring is not good because it ends up providing Google the same content for all pages rendered. This is the opposite of what should happen because, in order for good SEO rankings, Google should get unique pages and unique content for each page.
About the Author
Catherrine Garcia is an experienced Web Developer at WPCodingDev and a passionate blogger. She loves to share her knowledge through her articles on web development and WordPress.