Marko Vasiljevic

Hello Alexey,

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

Hello Gemma,

I am sorry about the issue you are experiencing and I am happy to assist you with this.
Please note that W3 Total Cache and some other caching plugins may not be allowed on certain hosting providers.
Please upload your screenshot here and share the image so we can check this.
Thanks!

Hello,

Thank you for reaching out and for a detailed explanation of the problem you are facing.
By default, the Auto-convert image after the upload is enabled in the W3 Total Cache Image Servce feature.
Most of the users do not want to bother and just because of that the option Auto-convert is always enabled.
You can disable this in Performance>Extensions>Image Service. Click on the Settings link and select the Disabled radio button in the Configuration area:

Once the images are translated, you can manually convert all images or a single image in the Media library.
I hope this helps!

Thanks!

Hello Pim,

Thank you for reaching out and I am happy to assist you with this.
We’ve received your email and I’ve replied with a detailed explanation about the potential issues you may be facing when caching the pages for logged-in users.
Please continue the correspondence there if you have any other questions so we can avoid duplicating the answers.
Thanks!

Hello Simon,

Thank you for reaching out and I am happy to assist you with this.
The optimal W3 Total Cache configuration takes into account a number of factors: your theme, your plugins, the technologies available on the server, and the details you supply when placing your order. Since everyone’s site and traffic and theme are different, there is no one size fits all solution.
So, I would recommend the Performance Audit solution.
This service also takes into account the idiosyncrasies of Web Performance Optimization (WPO) in a WordPress context. It means that WPO best practices have to be modified for WordPress because of how the application operates. The number of counter-intuitive realities could fill a small book.

This means that the best configuration for your site might not involve enabling Objec, database caching, and other things that you might expect. As a matter of fact, it can actually hurt performance by implementing features for the wrong situation.

The deliverable with this service is a faster site. It’s impossible to predict the extent to which our work will improve performance (especially true for code we didn’t write running on servers we didn’t build), but our promise is that we’ll do our best.

Additionally, we’ll send along a performance report that outlines the improvements, recommendations (if any), and what else we can do to help you reach and exceed your performance goals. There are many ways that we can help improve performance, you should think of W3 Total Cache configuration as the starting point for optimizing your site.

Upgrading to W3 Total Cache Pro makes this work even more effective, as we’ll have additional features to utilize in delivering the best possible results. It’s best to upgrade before placing your order since we can do this for you, and you can upgrade right in the Dashboard on any W3 Total Cache page.

I hope this answers your question.

Thanks!

Hello Yolandi,

I am sorry about the issue you are experiencing and I am happy to assist you with this.
W3 Total Cache is of course a plugin, and as a plugin, it uses drop-ins depending on the configuration.
advanced-cache.php means that the Page cache was/is enabled in the W3 Total Cache settings.
I would advise you to completely remove and re-install W3 Total Cache.
Please follow the steps below and if you cannot find the W3 Total Cache in the dashboard, please skip the first two steps:

1. Purge Cache
2. Deactivate and Delete Plugin
3. Check the .htaccess File (make a backup)
W3TC will create many directives in the .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
4. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– db.php (if exists)
– upgrade folder
– delete w3-total-cache folder in wp-content/plugins/ (if exists)
5. Delete Cached Files from CDN (if using CDN)
Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
6. Go to your wp dashboard and re-install W3 Total Cache

I hope this helps!

Thanks!

Hello,

Thank you for the information.
I presume that https://images.singletracks.com/blog/ is the CDN URL. Can you please share the website URL?.

Thanks!

Hello,

Thank you for your feedback, Can you please share the URL if the image that is showing converted in the media library?
As I’ve stated before, W3TC use the rewrite rules to serve images as webp.

Thanks!

Hello,

Thank you for reaching out and for your questions.
With W3 Total Cache Image service all images converted with the Image Service tool are sent to a third-party server maintained by the W3 Total Cache team which reduces resource consumption and allows for a large number of conversions in environments where resources can be limited such as shared hosting. Images sent to the W3TC server for conversion are only held temporarily and no permanent information is kept on the server regarding the images.

WebP optimizations with the Image Service tool do not replace the original image file and all conversions can be reverted without any loss of data.
W3 Total cache uses the rewrite rules so you can check your.htaccess/nginx.conf and the WEBP rewrite rules should be there.
I would also recommend checking if the image is converted (Use the image URL and change the extension to .webp) and also make sure that Imagic supports the webp for thumbnails and resized images.

I hope this helps!

Thanks!

Hello Lynn,

Thank you for reaching out and I am happy to assist you with this.
I’ve replied to your email, sharing all the information about the W3 Total Cache Pro license and access to manage your account.
If you have any questions, please follow up in the email correspondence so we can avoid duplicating the answers.
Thanks!

Hello Oren,

Thank you for reaching out.
I replied to your email on May 26, 2022, via the W3 Total Cache support channel, and the email used was oren@ however we never received a reply. I am not sure how your email was configured so you may want to check your spam folder.
If I understand correctly once the cookie is used and the user is logged in, the user receives the cookie-based cache. And once the user is logged out, the cache is no longer based on a cookie if I understand correctly, which seems to be normal behavior.
If I did not understand this correctly, please share more information and details.
Thanks!

Hello Graham,

Thank you for reaching out.
Can you please disable the settings one by one in Performance>general settings, save the settings and purge the cache after each setting is disabled and see which one might be causing the issue?

In Performance>Cache Groups>Manage User Agent Groups, you can Create (or simply enable the existing) a group of user agents by specifying names in the user agents field. Assign a set of user agents to use a specific theme, redirect them to another domain, or if an existing mobile plugin is active, create user agent groups to ensure that a unique cache is created for each user agent group. Drag and drop groups into order (if needed) to determine their priority (top -> down).
If you are not using any AMP, the only thing that you need to do is Enable both Groups (High and low), and select the theme that you are using in the dropdown menu to ensure that a unique cache is created for each user agent group. Drag and drop groups into order (if needed) to determine their priority (top -> down).

The two default User-Agent Groups are covering all notable groups. If you wish to add any other you can do so by Specifying the user-agents for these groups. Remember to escape special characters like spaces, dots, or dashes with a backslash. Regular expressions are also supported.
Make sure to save all settings and purge the caches once the groups are enabled.
Please make sure to check the screenshot below and let me know if this helps.

Thanks!

Hello Luis,

Thank you for reaching out and I am happy to assist you with this.
W3 Total Cache is load-balancer friendly and built from the ground up with the scale and current hosting paradigms in mind.
When using load-balanced servers or a server cluster, Memcached or Redis as a caching method are the best to use. It helps to share the cache between multiple servers.

I hope this helps!

Thanks!

Hello Vladislav,

W3 Total Cache uses the rewrite condition to serve the webp images. So you should see image/webp type once inspecting the source, which is not the case in your case and mostly because the images are mostly thumbnails, which suggests that the Imagic does not support the webp format and for this you should check with your hosting provider.
Thanks!

Hello,

Done. The invoice was updated and sent to the requested email addresses.
Thanks!

Hello,

Thank you for reaching out and I am happy to assist you with this.
I’ve made changes as requested and sent the invoice for W3 Total Cache Pro. I’ve deleted the information you shared since this is a public forum.
Thanks!

Hello Steven,

As I can see the W3 Total Cache Pro license is activated on 2022-05-25

If you still do not see the Pro version active, remove the license key from Performance>General settings, Licensing sub-box, license field, and save all settings. Re-enter the license, verify the license with the “verify license button” and save all settings.

W3 Total Cache Pro should be active after these steps!

Thanks!

Hello Adam,

First of all, thank you for the awesome review.
To answer your questions:

1. We do not have documentation on every CDN setting since all settings are self-explanatory and of course, it depends on which CDN provider you are using and if you are using Pull or Push CDN Type. However thank you for the idea, as this might be a good article. I will add explanations below:

Host attachments: when enabled, attachments (e.g. images from the media library) are served through the CDN.

Host wp-includes/files: when it is active the files of the wp-includes folder are served through the CDN.

Host theme files: when enabled the theme files are served through the CDN.

Host minified CSS and JS files: when enabled, minified CSS and JavaScript files are served through the CDN.

Host custom files: refers to the files specified in the Custom file list that you can see in the Advanced tab of this same page.

Add canonical header: This allows you to identify the original URL with the canonical tag. Generally, search engines are able to distinguish the URL without the need to specify it, so by default, the option is disabled.

Advanced

Only purge CDN manually: by default W3TC manages autonomously the purge of the cache. If you enable this option you will purge the cache only manually, normally you don’t need to enable the function, as this was specifically added for Cloudfront users because of the huge invalidation costs on the AWS side

Disable CDN on SSL pages: By activating this option you may run into the problem of mixed content. It happens when some contents are downloaded using HTTP protocol instead of HTTPS and the browser returns a not-secure site warning. In most cases, it is better to leave this option disabled.

Disable CDN for the following roles: This allows you to choose which user roles to disable CDN for.

2. Akamai CDN, as you can see is the origin pull, which means that the files are uploaded automatically to the CDN. Once uploaded, all images and files are served from the CDN. The CDN will not serve the image if it’s not uploaded to the CDN. In this case, the image will be served from the origin.

3. It’s recommended to use different filenames for each image. So if the situation you described occurs, you should try purging the cache manually for the CDN in the W3TC settings. The problem with this is not the CDN, but the Browser Caching. For images, it’s recommended to use 1 year caching for browsers (Expires header and cache-control header) so if the image has the same filename and a different image is uploaded instead, the browser will think it’s the same image and will not fetch for the new one. It’s recommended to use the option “Prevent caching of objects after settings change” in Performance>Browser Cache. This option adds the random query string to files (You can enable it only for images) for example: ?xNNNNN. This will ensure that the browser always fetches the new file from the source, in your case CDN, and all you have to do us to update the media query string in Performance>Browser Cache (Just above the general section), once new image is uploaded with the same filename.

I hope this answers your questions.

Thanks!

Hello George,

Thank you for reaching out and I am happy to assist you with this.
If the W3 Total Cache license is not renewed after a year, only the Pro features will stop working like FSD CDN integration or Eliminating render-blocking CSS.
All other features that come with the free version will still work as expected.
I hope this helps!

Thanks!

Hello Adam,

1. In the “Replace site’s hostname with” field, the CDN’s edge address should be added. This is used to rewrite the URL of the static resources as I’ve mentioned in the previous post.

2. This should be added in the Performance>CND>Configuration: objects section.

3. The CDN configuration depends on the CDN provider. You can always use Generic mirror and only add the CDN”s Edge address, or use Akamai from a CDN dropdown menu and configure the CDN with Username and Password.
You can check this article for more details about Image Service.

4. W3TC does not handle image resizing upon uploading a new image, so you can use some plugin for this.

Thanks!