Adnan Haque (a11n)

Hi @remouk,

My apologies, the link I provided was incomplete. Please try this link. It will look the same as the last one, but will show you a “Contact Support” button after submitting the initial question.

Hi @redthruviolet, Looks like your site is now serving critical CSS. Is the issue resolved for you now? If you are still facing the issue, please open a separate thread so we can focus on your issue specifically.

Hi @remouk !

We may need some additional information from you to find what’s causing this issue. Can you please reach out to us at https://jetpack.com/contact-support/. Please mention this thread when you do so.

Hi Philippe!

Can you please share the URL of your site?

Hi @antoniomanco!

That is the correct way to check the cache functionality.

It seems like you are using Cloudflare. Some cookies set by Cloudflare may be confusing the cache system. I have recorded that as an issue and we will work on a fix for that:

https://github.com/Automattic/jetpack/issues/39935

@susanna961 Please open a separate thread with more details (e.g., your site URL, what error you are facing, etc.). That way, we can help you effectively.

@samcheung729 I took a look at your site and looks like it’s serving critical CSS. Was the issue solved already. If not, can you share more details and screenshots of what you are facing?

Hey @bryanjohnson!

I couldn’t find any Jetpack connection to tomb of the mask. Do you still have Jetpack Boost installed?

Please open a separate thread so we can focus on your issue specifically.

@derrickg72. Please open a separate thread so we can focus on your issue without confusion.

Hi! Seems like you have the following script handles on the page:

• bodyscrolllock
• jquery-core
• jquery-migrate
• super-speedy-search-js
• smartmenus
• imagesloaded
• page-links-to
• heateor_sssp_sharing_js
• jetpack-stats
• jetpack-carousel
• elementor-pro-webpack-runtime
• elementor-webpack-runtime
• elementor-frontend-modules
• wp-hooks
• wp-i18n
• elementor-pro-frontend
• jquery-ui-core
• elementor-frontend
• pro-elements-handlers

My first guess is smartmenus based on the name. If not, it’s probably one of the scripts in bold.

So my advice is:

1. Try excluding smartmenus first.
2. If it doesn’t solve the issue, try to exclude each script in bold and see if it works.
3. If it still doesn’t solve it, try to exclude the scripts not in bold until you find the one that solves the issue.

Awesome! Thanks for letting me know.

Hi! It is possible that another cache plugin has created a wp-content/advanced-cache.php file. Usually the file would get deleted if you uninstall the previous caching plugins completely.

If you are still facing this issue after uninstalling the other caching plugins, you may need to manually delete the advanced-cache.php file from your wp-content folder. It should be safe to delete the file, but I still recommend that you create a backup of the file before you delete it.

Please let us know how it goes.

Hi Javier! I’m sorry you had to face this disruption. We want to investigate this issue so we can fix it for you and prevent it from happening to future users.

Please contact us at https://jetpack.com/contact-support/ so we can ask for more details privately. Remember to mention this thread in your message.

Hi Henri! I took a look at your site. Looks like you are already using CSS optimization from Lightspeed cache. As a result it’s conflicting with Jetpack Boost’s critical CSS generation.

It’s ok to use multiple optimization plugins. However, using similar optimization features in multiple plugins may lead to conflict and worse performance as a result.

For now, I recommend you only use the CSS optimization from either Lightspeed or Boost, depending on which better suits your site.

Hi!

It doesn’t seem like your site has a Jetpack connection. Can you please make sure Jetpack is connected to your site?

Thank you for narrowing it down to Jetpack Boost. Can you narrow it down to a specific module? You can disable all the Jetpack Boost modules and enable the modules one by one similarly to figure out which module is causing the issue.