Improve Wix Mobile Site Performance with Browser vs. Backend Rendering

In this video, we'll cover how Wix splits the rendering process into two cycles to improve performance, and how the Rendering API can help track code execution and selectively run parts of your code in certain conditions.

We'll start by discussing how Wix splits the rendering process into two cycles, with the first cycle happening server-side and the second cycle happening client-side. If it's not possible to split the rendering process server-side, all rendering happens client-side.

Next, we'll explore how the Rendering API can be used in your page's onReady() event handler to control where your code runs during the rendering process and to prevent code that causes side effects from running twice. We'll also show you how to use the wixWindow module to import the current environment the rendering process is running in, either "backend" when rendering on the server or "browser" when rendering on the client.

In the final part of this tutorial, we'll conduct some experiments to test whether rendering only on the browser can improve page load speed. By rendering only on the client-side, we can reduce the amount of time needed to set up the page on the server, potentially improving the overall speed of the site.