Instead, developers, webmasters and SEOs should use server-side rendering, static rendering, or hydration.
What is Dynamic Rendering Exactly?
Here’s an illustration of how it works:
Google shared this article on web rendering which explains why not all sites need dynamic rendering, and how there are better solutions out there.
Alternative Solutions For Dynamic Rendering
As mentioned above, Google recommends using alternative options and avoiding dynamic rendering:
- Static Rendering
- Server-side Rendering
This one should happen as you’re building your site. Generally, Static rendering involves creating separate HTML files for each URL in advance. As explained here, because HTML responses are generated in advance, static renders can be deployed to multiple CDNs and take advantage of edge-caching.
However, creating URLs in advance may be challenging. So, to use this method, you’d have to be very organized and have everything planned way ahead.
Server rendering is essentially just sending text and links to the user’s browser. The approach can work well for a wide range of devices and networks. It also allows interesting browser optimizations to be applied. You can read more about it here.
This achieves an FCP and picks up by rendering again using a technique called hydration. It is a new solution for things, so this approach can come with some serious performance drawbacks, like the page looking fully loaded but is actually frozen. Read more about this approach and its drawbacks here.