Title: disabled (query not cacheable) why?
Last modified: September 27, 2016

---

# disabled (query not cacheable) why?

 *  [neonWired](https://wordpress.org/support/users/neonwired/)
 * (@neonwired)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/disabled-query-not-cacheable-why/)
 * Is there any docs or explanation as to why certain queries aren’t cacheable

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [Scott Hartley](https://wordpress.org/support/users/destac/)
 * (@destac)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/disabled-query-not-cacheable-why/#post-8227021)
 * I believe that might be a pro only feature o.o
 *  [Kimberly](https://wordpress.org/support/users/amiga500/)
 * (@amiga500)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/disabled-query-not-cacheable-why/#post-8227141)
 * What cache mode are you using? Is it _Disk Enhanced_? And are you referring to
   the Page Cache option: `Cache URIs with query string variables` and why it is
   disabled for Disk Enhanced?
 *  [Scott Hartley](https://wordpress.org/support/users/destac/)
 * (@destac)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/disabled-query-not-cacheable-why/#post-8227958)
 * I see what he is referring too. Disk enhanced does not support the Cache URIs
   with query string variables by nature.
 * If you want better performance disk enhanced is the way to go disk basic is nice
   if you have access to things such as fragment caching where you need the flexibility.
 * I wouldn’t worry about caching those query string variable’s anyways.
 *  [hughforsyth](https://wordpress.org/support/users/hughforsyth/)
 * (@hughforsyth)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/disabled-query-not-cacheable-why/#post-8299928)
 * > I wouldn’t worry about caching those query string variable’s anyways.
 * [@destac](https://wordpress.org/support/users/destac/) strictly speaking it depends
   on the site and the percentage of page impressions containing a query string.
   If 90% of your traffic contains query strings then it is likely important to 
   cache that content, especially if that traffic happens to be your high value/
   paid for traffic.
 * Even if your permalink structure does not contain query strings, people/systems
   often use query strings for campaign tracking adding things like “?utm_source
   =twitter&utm_medium=social&utm_campaign=test-campaign” to shared URLs. WordPress
   will ignore these but they will be read by Google Analytics or other products.
   I do that when sharing things on social media so I can use Google Analytics to
   see what visitors from Twitter did. If I’m not caching URLs with query strings
   then I’m ensuring visitors clicking on a link in Twitter get a slower experience
   and use more server resources than visitors clicking the link elsewhere without
   a query string. If something happens to do well (“go viral”) then that could 
   be the majority of traffic for a day not being cached.
 * Similarly Google Adwords adds query strings for tracking so if you are not caching
   these then you will be giving a slower experience to the people you’ve actually
   paid money to get to your site. One site I look after gets 80% of its traffic
   from Adwords (URLS with a query string). It does not make sense to serve content
   more slowly to the people they paid to acquire.
 * So yes, sometimes caching content with query strings does matter and sometimes
   it matters a lot.
 *  [hughforsyth](https://wordpress.org/support/users/hughforsyth/)
 * (@hughforsyth)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/disabled-query-not-cacheable-why/#post-8324996)
 * > Similarly Google Adwords adds query strings for tracking so if you are not 
   > caching these then you will be giving a slower experience to the people you’ve
   > actually paid money to get to your site. One site I look after gets 80% of 
   > its traffic from Adwords (URLS with a query string). It does not make sense
   > to serve content more slowly to the people they paid to acquire.
 * Just to clarify something in my previous comment. If you are using auto tagging
   in Adwords this will effectively add a cache busting “gclid” query string to 
   every link. In this case you are pretty much guaranteed a cache miss and page
   rebuild so query string caching may not add much and could even be detrimental.
 * OTOH, if you are manually tagging campaigns in Adwords with UTM parameters then
   you may get a beneficial hit rate as there will be more repeated query strings.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘disabled (query not cacheable) why?’ is closed to new replies.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

## Tags

 * [cache](https://wordpress.org/support/topic-tag/cache/)
 * [query](https://wordpress.org/support/topic-tag/query/)

 * 5 replies
 * 4 participants
 * Last reply from: [hughforsyth](https://wordpress.org/support/users/hughforsyth/)
 * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/disabled-query-not-cacheable-why/#post-8324996)
 * Status: not resolved