A great way to see if Google is struggling to render a website’s page is using Google’s Mobile-Friendly Testing Tool and Google Search Console’s URL inspection tool. Both tools will allow you to see what elements and content Googlebot is choosing to crawl and render in comparison to what the user sees.
You can also use DevTools by right-clicking on the page and then going to inspect. This will allow you to see the page’s rendered DOM after all scripts have been parsed by the browser. This can then be used to cross-reference with Google Search Consoles rendered HTML to see if there are any discrepancies.
How to check if your website is caching?
There are multiple ways to see if your website is utilising browser caching. However, the most reliable method is using DevTools. If you open your website with DevTools and navigate to dev tools settings in the network section, you can disable caching. This will enable you to see what the page looks like with and without cache to determine if there are any differences.
Another way to check your website’s browser caching is by running a lighthouse report in DevTools, which will list all resources not leveraging browser caching.
Another way to check this on a page level is in the dev tools coverage tab. When looking at the line by line breakdown view, you’ll be able to see how much of a resource has been used by the browser on the page with a visual representation.
How to troubleshoot for web workers?
The best way to see if your website is already using a dedicated web worker is by navigating to the dev tools sources tab when on your website, and it should be stated in the code tree or through the Application tab under ‘Service Workers’.
How to know if your website should move to server side rendering?
1. Efficient browser caching
Once a user has visited the site and loaded all the pages on their device, the resources that have been cached locally will load quicker when they revisit the site as they no longer require requests from the server.
2. Eliminate render blocking
4. Implement web workers
5. Server side rendering
It’s worth highlighting that server side rendering is more expensive in comparison to client side rendering, which could be a contributing factor to why businesses may not choose this mention of rendering for their site.