In case anyone else runs across this, it looks like something mysterious happens to the standard Google Analytics query strings such as utmsource. html_gzip files, along with folders for each page on your site. Basically GoDaddy hosting does something special to utm-type query strings. This is the folder where you should find cached. Inside of that folder, you should see a folder named like your domain. Access your WordPress file system and navigate to:.Make sure you’re logged out, then visit several pages on your site, so they get cached.Using either (S)FTP, or your web host’s file manager panel, you can visit the cache folder in your WordPress install directly, and make sure that cache files are generated correctly. Go to Wappalyzer to install browser extension You’d just install one of their browser extensions that will show you if WP Rocket is running on a website. Wappalyzer is a free service that lets you identify technology on websites. And as you described does not cache additional parameters. (as expected) serves the same cache file for all values of test. This means that WP Rocket’s file optimization is working usually, the page would also be cached. ScottTravisHartley commented on Then WP Rocket (as expected) creates a different cache file for each value of test Creates a different cache file when & is present. Open the browser’s source view of the page and look at the section. This methodology works if you have Minify or Combine for CSS files or JavaScript files on the File Optimization tab enabled. Not seeing a footprint at all? Are you perhaps using Cloudflare? Cloudflare’s HTML minification would remove the footprint. This will happen when caching is disabled as part of hosting compatibility, or if you are using a specific helper plugin to do this. In some scenarios, where WP Rocket's page caching is disabled but other optimizations are still applied, the footprint will be present but without the timestamp. At the very end you should see an entry like this: Open the browser’s source view of the page and scroll to the bottom. Now that we’ve made sure you’re visiting a page that indeed is expected to be served from cache, here’s how you can identify it really is cached: 1. Steps 1, 2 and 3 below will still be relevant. Please check our hosting doc for host-specific notes. If you are on a Managed WordPress host, page caching may be disabled by design.
0 Comments
Leave a Reply. |