So how does dynamic rendering work?
This process been broken down into a diagram below
Technical implementation of dynamic rendering
In order to implement dynamic rendering on your website, there are some key elements you must take into consideration.
To solve this, we must introduce a caching layer within our dynamic rendering infrastructure. See the diagram below to help illustrate.
Pre-rendered (static HTML pages) pages should be cached. This means that the page has already been built in the background, therefore does not need to be re-rendered on the fly when Google requests it.
Cached pages can be served to Google in under 200ms, whereas doing it on the fly will take anything from 5 seconds at best to 10+ seconds.
Note: we have seen large websites lose over 50% of their organic traffic due to pre-rendering on the fly, resulting in Google not being able to access/crawl the website properly. We can’t stress enough how important it is to not do this! Remember, high time to first byte signals to Google that your servers are unable to handle the traffic, which causes Google to slow down. Imagine time to first byte that’s 1,000%+ over Google’s recommended 200ms limit!
I will not go into the details of caching and how it all works in the background, however if it is something you are interested in. Please do contact us and if we gain enough interest we can go into comprehensive detail.