Remove Query Strings from Static Resources in WordPress

What query strings are (cache busting)

First, what these strings are: WordPress appends ?ver=X.Y to enqueued CSS and JavaScript URLs so browsers and CDNs fetch fresh files when versions change. Speed tools flag them because some CDNs and proxies historically refused to cache URLs carrying query strings.

Method 1 — the plugin toggle, the right choice for most sites:

• WP Rocket: Basic Options > 'Remove query strings from static resources' — enable, save, purge cache.

• Autoptimize: its CSS/JS options strip query strings as part of optimisation (its file aggregation also solves the warning by rewriting asset URLs entirely).

• LiteSpeed Cache: the optimisation module handles CSS/JS combining in ways that largely moot the warning on LiteSpeed stacks — where WebJi® hosting runs, the question usually dissolves.

After enabling anything, purge all caches and verify a stylesheet URL in view-source: the ?ver= should be gone.

Why speed tools flag them

How this plays out with query strings on static resources (?ver=): settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

Method 1: plugin toggle

plugin toggle. Update plugins and themes on a copy or straight after a backup, one at a time if the site is a shop. A white screen after an update is usually one plugin: rename its folder via the file manager to disable it. Remove plugins you do not use — they are unpatched code.

Method 2: functions.php filter

functions.php filter. Pick the newest PHP version the site's plugins actually support, set it in the panel, and load the homepage plus one form. If the site whitescreens, switch back and read the error log before you try random plugins. Do not leave a shop on a PHP release that no longer gets security fixes.

The file-update caveat

The file-update caveat. Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.

When NOT to remove them

On remove_query_arg filter snippet, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Verifying with speed tests

Verify like an engineer, not a checklist-follower:

1. Before: run GTmetrix/PageSpeed, note the warning and the actual waterfall rows for your CSS/JS — are versioned files really being re-downloaded, or cached fine?
2. Apply your chosen method.
3. After: view-source on a fresh page — asset URLs lack ?ver=; hard-reload — styles and scripts still load.
4. Re-run the tool — the warning should clear; and crucially, check the waterfall again: if the files were caching fine before, nothing improves — you have traded a warning message for cache-busting risk.
5. The one-week test: update a plugin with visible changes and confirm returning visitors see the change, not cached stale CSS.

If anything misbehaves, revert the toggle, purge, and rest easy: the warning was cosmetic, the breakage would be real.