Performance Optimization
      Back to home
      1. Help Center
      2. Configuration
      3. Performance Optimization

      How to avoid a low Cumulative Layout Shift (CLS) score due to the Google Page Experience Update

      THIS ARTICLE WILL HELP YOU:


      What is the Google Page Experience Update?

      Google recently announced a new algorithm that would rank web pages based on the visitor's experience of interacting with the web page.

      The Page Experience update will be officially rolled out in mid-June. But you can still look up the Core Web Vitals score for your website under the Lighthouse section of the Google Web Developers Tool or with a tool like GTMetrix. 

      We have tested the Convert script and we have found that its implementation does not affect the CLS score. 

      Our recommendation

      To avoid a low Cumulative Layout Shift (CLS) score, we recommend the following:

      1. Plan your variation implementation to not affect the CLS score. Make sure your code or WYSIWYG change does not cause layout shift, and that the dimension of the main components of your page does not change, as part of the experiment.
      2. Find your variation CLS Score by using Forced Variation URLs to trigger your experiment and find out the score with a CLS tool. You can use the Lighthouse Page Analitycs component of Chrome Developer Tools under Performance. This will provide you the score and will point to any issues you may have regarding Layout Shifts. You can do this under QA mode to prevent your general visitors to be affected by this.
      3. If you already have a considerable CLS Score already, do the same as the previous point, for each of the variations/deployments running. This will allow you to detect what variation/deployment is causing the issues, and then fix it or pause it.

      If you still have a considerable CLS score after following the points above, contact support, and let us know so we can help you diagnose the issue.