At present,97 URLs are affected by CLS issue more than 0.25 (desktop) and 85 URLs affected by LCP issue: longer than 4s (mobile) on our website.
Website - www.sopact.com to look into it.
How can we fix these issues?
Thank you in advance.
At present,97 URLs are affected by CLS issue more than 0.25 (desktop) and 85 URLs affected by LCP issue: longer than 4s (mobile) on our website.
Website - www.sopact.com to look into it.
How can we fix these issues?
Thank you in advance.
Run some of the affected pages in Page Speed Insights. Select desktop as that is your biggest problem area. The tool has a "Show audits relevant to" option where you can select CLS. The report will then show only issues related to causing Layout Shifts on desktop devices.
Expand each issue to get more details on what is causing the issue and sometimes what to do to fix it.
If you want to dig deeper the Chrome browsers Performance tool can provide a lot of details. It also lets you throttle your browser so you can more easily see the layout shifts happening.
If you enable screenshots you can hover along the screenshot row to see how the page changes as it loads. Make sure you start hovering at the point the new page is loading as the initial part shows the previous page before it is replaced.
I have the feeling in your case you have elements that are off screen expanding your main div as they load, and causing it to shift. The Page Speed Insights lists some element that could be adjusted so that they don't expand the div as the load. e.g. define their height in advance.
There is a page test tool which tells you more about your CLS rating: https://www.webpagetest.org/
I am not sure if this tool is somehow related to Google, but in my case it outputs the same CLS rating.
If you have a close look you will recognize that this tool is not able to do parallel loading. And I assume this is same for the module which Search Console uses. Real world browsers load files in parallel which shortens loading times drastically. This one does not - so you get loading times of several seconds for bigger pages. Well, fonts are loaded after CSS and images. In my case the delayed loading of fonts (several seconds later) caused the problem.
To improve the loading time in a sequential environment you can use certain preload technologies.
<link rel="preload" href="/fonts/anyfont.woff2" as="font" crossorigin />
The tag above will advice the browser (and Google's tool) to load the font upfront. When it is loaded in your CSS later, it will already be available in the cache.