Raam Dev

You just need to make sure the following is in your .htaccess file (if this isn’t working, I recommend double-checking with your web hosting company, in case their server configuration is different):

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

For static resources, your web server sends the If-Modified-Since headers with those requests. Requests for static resources don’t even go through PHP or WordPress, so Comet Cache wouldn’t have any effect on them.

@martychc23 For a long time, WordPress Core itself removed the If-Modified-Since header and when Comet Cache was originally written it followed that same behavior, because the If-Modified-Since header is tricky to do in such a dynamic environment like WordPress.

However, WordPress Core has since added support for sending the If-Modified-Since header (or rather, it has stopped automatically removing it), however Comet Cache has not yet been updated to support this.

We do plan to change this in a future release to allow the If-Modified-Since header and there’s a GitHub issue here with a comment describing the current state of Comet Cache + If-Modified-Since: https://github.com/websharks/comet-cache/issues/255#issuecomment-304394481

I recommend following that GitHub issue for updates.

@username201701 “Combine external JavaScript” and “Combine external CSS” can be accomplished with the HTML Compressor feature, which is included with Comet Cache Pro. Otherwise, you could use another free plugin like Autoptimize.

“Leverage browser caching” is also a feature of Comet Cache Pro. Technically browser caching is a feature of your web server, not of Comet Cache, but Comet Cache can add the necessary rules to your .htaccess file with the Apache web server.

“Remove query strings from static resources” is not really recommended for WordPress sites as many resources use version-specific static resources that require including the version number as a query string. Query strings have minimal impact on performance.

• This reply was modified 8 years, 11 months ago by Raam Dev.

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

@stevenw123 Here are a few possible reasons off the top of my head:

• You’re testing different pages, some which are already cached and some that are being cached the first time. When a page is cached for the first time, that visit is going to be slower than subsequent visits. (The Auto-Cache Engine can help resolve that.)
• You’re using a shared web host where other sites on the server may affect the performance of your site from moment to moment.
• Your web hosting company is experiencing network issues.
• The network route between the GTMetrix testing server and your server is experiencing issues.
• GTMetrix is experiencing issues with their testing servers, resulting in differing results. You could try using other speed testing services to confirm this isn’t the issue.
• Your WordPress site has a lot of active plugins and/or custom code running—in certain cases, this could negatively affect performance.
• Comet Cache isn’t actually running. See How do I know if Comet Cache is working?

To exclude this page from be cached by Comet Cache:

http://golfoasen.se/nyheter/

You should add the following to Comet Cache → Plugin Options → URI Exclusion Patterns:

/nyheter/**

For more information on the syntax for that field, please see this article.

@hectornado Comet Cache is a page caching plugin, which means it captures the output from WordPress and stores that output in a static HTML file, only updating the static HTML file when the WordPress content changes.

For that reason, any plugins that produce dynamic content (such as the Custom Facebook Feed plugin) must take into consideration WordPress caching plugins, either by telling the WordPress caching plugin not to cache the page where the plugin is located, or, even better, making use of client-side JavaScript to dynamically update the content so that the plugin is unaffected by server-side caching.

If the Custom Facebook Feed plugin is not compatible with WordPress caching plugins, you can exclude the page where the Facebook feed shows up by excluding the URI of the page in Comet Cache → Plugin Options → URI Exclusion Patterns. Otherwise, I recommend contacting the plugin developer(s) for Custom Facebook Feed and asking them about compatibility with caching plugins.