Marko Vasiljevic

Hello Jihyun

Thank you for reaching out, and I am happy to help!
Just to confirm, have you tried restarting the Redis instance and trying the default IP: Port in the W3 Total Cache Object Cache settings for Redis?
Thanks!

Hello Rene,

Thank you for reaching out, and I am happy to help!

Can you please reach out directly to us via the W3 Total Cache support channel via the plugin in Performance>Support>Billing, or via the email customer-support@w3-edge.com, and provide the information about your organisation and how many licenses you need.

This is a public forum, so we should not share sensitive information here.

Thanks!

Hello Mark,

Thank you for reaching out, and I am happy to help!
We’ve received your email via the W3 Total Cache support channel and replied to it!

Thanks!

Hello Sean,

Thank you for reaching out, and I am happy to help.
Since this is a public forum, can you please reach out directly to us via the W3 Total Cache support email customer-support@w3-edge.com and provide details about your subscription, like the license key and the website in question, so we can assist you with your request?
Thanks!

Hello Harry,

Thank you for reaching out, and I am happy to help!

Can you please share how this is related to the W3 Total Cache??
Thanks!

Hello Robert,

Thank you for reaching out, and I am happy to help!
As with any other plugin, W3 Total Cache can be deleted via the plugins section in the WP-Admin area. W3 Total Cache is a robust plugin as it offers a lot of possibilities for optimization. This being said, there are a lot of files; however, the W3TC is not responsible if the files are not deleted from the server when removing the plugin. What happens is that the hosting restrictions, especially when it comes to permissions, may cause some residual files to remain on the server. I assure you, the W3TC, when being removed, is like any other plugin; however, you can always do this manually

As for the other question regarding the CSS issue you are experiencing, this is why the W3 Total Cache is the best optimization solution, as it offers something called Cache-busting
The option “Prevent caching of objects after settings change” in Performance>Browser Cache can be enabled for individual files, and it can be enabled for all CSS and JS files under the CSS&JS section in the Browser Cache. Since the suggested expiration for the static files is 1 year, the “cache-busting” can be achieved with the Prevent caching of objects after settings change, which adds the query string to the file, and once updated, the browser will naturally fetch a new version since it’s not the same file
For example, if the option is enabled on the plugin that has a file https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css the query string will be added:

https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css?x1234

If the content of the CSS file is changed, and the option “Prevent caching of objects after settings change” is enabled for CSS&JS files, all you have to do is to update the media query string using the “Update media query string” button in the Performance>Browser Cache at the top of the page, which will then update the string and force the plugin to fetch the new version:

https://website.com/wp-content/plugins/some-plugin/css/some-css-file.css?x4231

After updating the query string, you also need to purge the cache.

I hope this helps!

Thanks!

Hello Mauro,

Thank you for reaching out, and I am happy to help!
I’ve replied to your request via the W3 Total Cache support channel. Please check your email and continue any correspondence there so we can avoid duplicating the answers
Thanks!

Thanks!

Hello Daniel,

Thank you for reaching out, and I am happy to help!
Please reach out directly via the W3 Total Cache support channel in the plugin – Performance>Support>Billing and provide information about your subscription so we can avoid sharing sensitive data in a public forum!
Thanks!

Hello Dawid,

Thank you for reaching out, and I am happy to help!
Remove the license key from W3 Total Cache Performance>General settings, Licensing sub-box, license field, and save all settings. Re-enter the license and save all settings.

W3 Total Cache Pro should be active after these steps!

Hello Chris,

Thank you for reaching out, and I am happy to help!
When you subscribed to the W3 Total Cache Pro, you received an email with the license key and the invoice, and you can reply to that email to request any assistance with the W3 Total Cache billing.
This email also contains the link to manage your subscription and check the invoices.

You can also reach out to us directly via the plugin in Performance> Support>Billing and ask any questions about your subscription.
Also, reach out to us directly via this contact form

We’ll be waiting for your email

Thanks!

Hello Tiziano,

Thank you for reaching out, and I am happy to help!
I’ve reset the active URL
Make sure to add the W3 Total Cache license to the prod website and save the settings.
Once added, add the constant to the dev environment, and re-save the license there
Thanks!

Hello Kaula,

Can you please disable minify in Perfirmance>General settings, save all settings and purge the cache and see if the issue persists?
If the issue is gone, re-enable minify, and disable the settings in Performance>minify one by one (HTML minify, JS minify, CSS minify) and see which one might be causing the issue.
Make sure to save all settings and purge the cache after each option is disabled.
Thanks!

Hello John,

Thank you for reaching out, and I am happy to help!

The deactivation of the plugin may not be directly related to the W3 Total Cache itself, but may have something to do with the permissions set on the server.
I’m sorry to hear about the trouble you’re having after activating the plugin — that definitely shouldn’t be happening, and I understand how frustrating it is when your site slows down like that.

Let’s get things back to normal quickly. Here are a few steps you can try:

Force deactivate the plugin:

Go to your site’s File Manager (via iPage control panel) or connect with FTP/SFTP.
Navigate to /wp-content/plugins/.
Rename the plugin folder (for example, change w3-total-cache to w3-total-cache-disabled).
This will automatically deactivate the plugin in WordPress.

Clear any residual cache files:

In the same directory, delete the /wp-content/cache/ and /wp-content/w3tc-config/ folders if they exist.
Also, check your .htaccess file for any leftover W3TC code blocks (they begin with # BEGIN W3TC and end with # END W3TC) and remove those lines.

It would be great if you could reach out to us directly via the plugin in the Performance>Support section so we can assist you without sharing any sensitive information

Thanks!

Hello Caroline,

Thank you for reaching out, and I am happy to help!
I’ve checked your website, and as I can see, one of the things that impacts your website’s LCP is rendering blocking requests.
This being said, in order to eliminate render-blocking CSS or JS, first you should minify the files with the W3 Total Cache. Minifying files helps by reducing a website’s loading time and bandwidth usage by removing unnecessary characters like spaces, comments, and line breaks from code, making the files smaller without changing their functionality. This leads to a faster website for users, which improves their experience and can positively impact search engine rankings.
Once the files are minified, both CSS and JS, you should go to advanced settings and choose the embed type for JS files to and for CSS files simply enable the option to Eliminate render blocking CSS by moving it to HTTP Body.

Please let me know if this helps and if you need more details, and if you have any other question about this

Thanks!

Hello Luzio,

Thank you for reaching out, and I am happy to help!

I’ve checked both URLs u shared:
The first one that contains a query string has an output:
Mise en cache de page à l’aide de Disk: Enhanced (Requested URI contains query)
By default, the W3 Total Cache, when using Disk: Enhanced, does not cache URIs with query strings. So the output means that the feed is not cached, because it contains a query string.

As for the pretty URL, the output is:
Mise en cache de page à l’aide de Disk: Enhanced (Requested URI is rejected)
As you can see (Requested URI is rejected) means that the feed is not cached.

In both cases, this is excluded from the cache

Please let me know if this answers your question and if there is anything else I can help you with
Thanks!

Hello Kayla,

Thank you for reaching out, and I am happy to help!

I’ve checked your website, and the score is looking good!

What you should also do is to preload the LCP image: https://www.kelanabykayla.com/wp-content/uploads/2025/01/sidemen-floralbath-kids-view-scaled.webp
And also, make sure to eliminate render-blocking CSS and JS

Have you configured the W3 Total Cache plugin accordingly?

Thanks!

Hello Steven,

Thank you for reaching out, and I am happy to help!

Your W3 Total Cache Pro subscription is now canceled, and no additional invoices will be issued for this subscription.

Thanks!

Hello David,

Thank you for reaching out, and I am happy to help!

Just to confirm, you wish to cancel the W3 Total Cache Pro renewal?
Can you please reach out to us directly using this contact form and provide the information about your subscription so we can avoid sharing sensitive data on a public forum?
Thanks!

Hello Mark,

Thank you for reaching out, and I am happy to help!
You posted this in the W3 Total Cache forum section. Can you please confirm that the issue is related to the W3 Total Cache?
And if so, does the issue persist if you temporarily disable the W3TC?
Thanks!

Hello Simon,

Thank you for your feedback
The widget is located in the Dashboard section of the W3 Total Cache. So under the Performance section, as shown in the screenshot in my previous reply, click the “Dashboard”. Scroll a bit, and you’ll see the Google Page Speed widget as shown in the screenshot below:

Let me know if this helps!
Thanks!