Title: Worker Cache Improvement
Last modified: July 16, 2022

---

# Worker Cache Improvement

 *  Resolved [Fody](https://wordpress.org/support/users/fodisery/)
 * (@fodisery)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/worker-cache-improvement/)
 * Hi,
 * I have feature suggestion to increase worker cache hit percentage:
    # Remove 
   empty query string parameters. for example: example.com/? can be rewritten to
   example.com # Sorts query string parameters alphabetically

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [iSaumya](https://wordpress.org/support/users/isaumya/)
 * (@isaumya)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/worker-cache-improvement/#post-15833805)
 * Hi,
 * > # Remove empty query string parameters. for example: example.com/? can be rewritten
   > to example.com
 * – That seems super odd. Generally there never is any blank query string start
   like you have shown i.e. `https://example.com/?` (unless someone has made a major
   mistake while adding the link)
    There always be some parameters there i.e. `https://
   example.com/?foo=bar`. Now the worker code already removes many unnecessary query
   parameters from the URL like”
 *     ```
       'fbclid',
         'fb_action_ids',
         'fb_action_types',
         'fb_source'
       ```
   
 * and stuffs like that.
 * But removing a blank query sting seems very odd and wired. Also it would create
   many issues as inside the worker code we doesn’t interpreter an URL as a string
   but rather we parse it as a URL(). So, I honestly don’t think it would create
   a problem as when the worker parse it back to string if there is no query param
   then it would just be `https://example.com/`.
 * > # Sorts query string parameters alphabetically
 * – If you have Cloudflare business plan or above you can just do it inside the
   Cloudflare Dashboard with a flick of a button. So, it makes no sense to replicate
   the same – increase the worker code unnecessary and increase execution time.
 * Moreover from my experience I would say even if you have CF Business or higher
   plan, don’t turn on this option as it will cause a lot of problem in WordPress
   and in many different plugins. There are many plugins like EDD and others who
   replies on the exact position of the query strings. So, sorting then always break
   things which are hard to trace and fix.

Viewing 1 replies (of 1 total)

The topic ‘Worker Cache Improvement’ is closed to new replies.

 * ![](https://ps.w.org/wp-cloudflare-page-cache/assets/icon-256x256.gif?rev=3234997)
 * [Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals](https://wordpress.org/plugins/wp-cloudflare-page-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-cloudflare-page-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [iSaumya](https://wordpress.org/support/users/isaumya/)
 * Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/worker-cache-improvement/#post-15833805)
 * Status: resolved