Raam Dev

@edouardflowasia Thank you very much for the 5-star review! 🙂

If post your ideas for improvements to the settings page design on our community forum, we’ll gladly take them into consideration.

@qbaniche73 I confirmed that Comet Cache is running properly on your site.

I ran your site through Google PageSpeed and Pingdom Tools and it looks like these are the items that are still having an impact on your site speed:

• Combine external JavaScript
• Combine external CSS
• Leverage browser caching
• Minify HTML
• Minify CSS
• Minify JavaScript
• Optimize images

Comet Cache Pro can handle all of those except the last one (Optimize images). For optimizing images, I recommend the great EWWW Image Optimizer plugin, which works well with Comet Cache.

@pdgrzdv I reviewed the WooCommerce source code to see how those language files are loaded and from what I can tell it should work just fine with Comet Cache page caching.

Have you tried running another page caching plugin (e.g., WP Super Cache) to see if you run into the same issue? If so, then this sounds like a WooCommerce incompatibility (or bug) with WordPress caching plugins in general and you should check with them to see if it’s something that can be fixed.

Comet Cache simply caches the output from WordPress. If WooCommerce loads the language translation files and outputs the content with the correct language, then that’s what Comet Cache will cache. If it outputs the content with the wrong language, Comet Cache will cache that as well. Comet Cache doesn’t ‘cache language files’ at all—it simply caches the output of WordPress.

I hope this helps. Let me know if you have any other questions. 🙂

@martychc23 Comet Cache Pro adds the following to the .htaccess when you enable Leverage Browser Caching. If you want to enable Browser Caching, here’s what you can use:

# Enable browser caching.
FileETag mtime size

<IfModule expires_module>
  ExpiresActive on
  ExpiresDefault "access plus 1 week"
</IfModule>

@martychc23 Does the Referrer-Policy header work if you disable Comet Cache?

@bigbluesquid The only thing that Comet Cache uses symlinks for is the 404 Error Page caching (Comet Cache → Plugin Options → 404 Requests). Since the 404 Error Page is the same regardless of where it’s loaded from, Comet Cache creates a single 404 Error Page cache file and then symlinks other 404 cache file paths to that original 404 Error Page cache file. This improves performance and saves disk space.

If your hosting service disables the PHP symlink() function, you can simply disable the 404 Error Caching feature in Comet Cache (see Comet Cache → Plugin Options → 404 Requests) and that should resolve the issue for you.

@zackdn Thanks so much for the awesome 5-star review! 🙂

We put a lot of time and effort into making Comet Cache simultaneously powerful and easy-to-use, so I’m really happy that you found it to be exactly that. Cheers!