HTTP Archive and CrUX have given the data that every year a 3 times increase in the performance of Wix sites has been seen when in the metrics of Core Web Vitals (CWV) a score of 75th percentile has been achieved by Wix sites. All this has become possible when the runtime of our website has been combined with CDN capabilities, cloud providers and industry standards and we took benefit from this.
No update has occurred in a large number of sites supported by Wix and for Wix it is a great challenge. But why is it a challenge? The search ranking of Google has included the page experience signals in the year 2021 and in the month of May. Faster web and improved performance visibility have been taken into consideration by the industry recently. It has been found that businesses’ revenues and conversion rates are directly impacted by the speed of the site. There are a number of intricacies, a lot of variables and beautiful complexity in the area of performance.
Performance scores and complexity of the site
Nowadays custom code, solutions of e-commerce, blogs and documents are not the only task for the sites. These sites have to handle several other applications and for this the sites need to be sophisticated and complex. If we use a CDN for serving a website and along with this if we use HTML in it then its instant loading can take place.
A lot of capabilities of doing business are provided by the templates of a large variety that are offered by the Wix. But the performance can be affected because of these extra features.
Use of HTML at the start
For running and rendering the website, the browser logic and client requests that are additional are triggered by the response from HTML. If you take interest in retrieving the document of HTML then the URL will get a request initially at the time of loading of the webpage.
Rendering at the client side in the earlier years
An empty document of HTML that was common was given to us and it was enabled by CSR. The operational costs of the backend that are so high are not meant for the sites that are of high scale. All this happens at the client side when the JavaScript was used for generating HTML content. This is known as the rendering at the client side that Wix performs.
Rendering at the server side in today’s time
In order to optimize the performance, the slower device’s visibility experience was improved by following this approach. If JavaScript is not supported by the search engines, then these search engines can index better if we improve the visibility times of the initial page. It will be good for the performance as well as for SEO and is known as rendering at the server side.
What will happen if in more than one location we use caching?
There were some caveats in using static HTML:
- Caching of all pages is not possible.
- There is a possibility of different HTML to be seen if the same site is visited by two people. So, we can say that visitor specific cookies and data are present in it.
- Frequent changes can be seen in it.
How to use a CDN solution that is in-house?
When the visitors were allowed to visit the content closely then the servers and the clients’ network latency was reduced with the additional locations used for serving sites.
Reduction in the complexities
The end user was able to closely view the content with the reliability improvement when in the phases of FCP and TTFB a substantial improvement in the performance happened because of cache implementation. But if you want to improve the performance then you need to remove the complexity that is not required and this complexity arose when each response needed an HTML modification.
HTTP/2, SSL and DNS
All the new connections come with some overhead. Now this overhead and all the required connections can be reduced if each user domain uses HTTP/2. For improving SSL times, connection and DNS you will get a lot of help from monitoring and network infrastructure enhancement.
If someone takes interest in creating custom websites then it will be good for him to contact a web development company.
