Warning..!

  • Removing query strings is all well and good, but understand that they’re there for a reason. You can always adopt another cache-busting technique such as changing the actual filenames of the static resources, or enqueing with a version number in the filename and using rewrites to resolve to the unversioned filename.

    None of this helps you with the versioning of static resources used by your plugins. If you update a plugin (or theme for that matter) and a static resource used by that plugin is updated and you use query-strings-remover to strip the updated query string, your users will still be using the cached version. This is likely to break your site until the cached resources expire which depending upon your headers could be a year or more.

    DO NOT use this plugin unless you fully understand the implications..!

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

  • I was about to add a review commenting this. I thought the same when I saw this plugin featured here: https://kinsta.com/knowledgebase/remove-query-string-from-url/

    People might be using it without fully understanding its implications. ??

    Well said ??

    Totally agree. Removing query strings in WordPress might marginally improve performance (might!), but at the cost of introducing bugs.

    Not worth the risk or the maintenance problems.

    I was about to add this plugin. From above Im not sure. Ironically, I did not have this PROBLEM AT ALL,,, until I started to get comments on my blog post. Gravatars and scrolling did not help at all. I still cant get baack to 100 on pingdom and gt metrix and page speed, as long as I have comments on my blog. ??????????

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Warning..!’ is closed to new replies.