Cs-classic loading, and causing errors in page speed insights

[oriol]

Hi there, please see here: https://staging-logoglo-newsite.kinsta.cloud/

the js file cs-classic is loading, and in google pagespeed insights, it is saying:

“Does not use passive listeners to improve scrolling performance”

It seams to be with the latest updates…this site: https://designtwentytwo.com/

hasnt been updated, and that js file doesn’t show, and doesn’t error:

Is there a fix for this?

[tristup]

Hi Oriol,

Thanks for reaching out.
The page speed issues are mostly related to the content,image, and scripts used in your site and beyond the scope of our theme support. If you want to increase the page speed, you need to ask 3rd party developers to help you with this or you can avail of our newly launched product called Boost, where we help you with your site speed optimization.

Thanks

[oriol]

Im not asking about page speed issues, I am aware of what needs to be done there, Im asking why the theme is using cs-classic? instead of the script that doesn’t cause this issue. In the site that is using an older version of pro, the issues aren’t there, and its not using cs-classic…why in the latest update is it using this?

There are clear issues in the script the theme s currently using…this shouldn’t need an extra service to fix, this is in the core files of the theme. You should be adhering to google best practices.

Is there a chance this will be addressed in upcoming versions?

[christian]

Hey @oriol,

cs-classic JS is just similar to cs JS in Pro 5.1.5 and I could not replicate your PageSpeed Insight issue on my site given it’s optimized properly.

With that said, there is nothing on our side to fix except that continuous work is needed to improve the overall theme performance.

Our Boost service would still be needed if you want us to fix speed issues in your site.

Thank you for your understanding.

[oriol]

Thanks, my site is optimized too, my issue is the old 5.1.5 js didn’t throw up any errors in google page speed, while the new one does…and this error is for the mobile page speed stats, not the desktop…its an error, so I do hope that in future releases, it will be addressed. Thanks.

[ruenel]

We will note your feedback, @oriol.
You are most welcome as always.