It appears Speed Optimizer (SO) removes the query strings from the files shown in the JS Combine and JS Deferral exclusion list. Why?

Details: https://prnt.sc/Gd__3EG5WqE9

The above sometimes creates issues with other performance plugins which utilize the entire file name (with query strings). If using two performance plugins, for example, jQuery could be cached twice (the file with and without query strings) and create page display issues downstream.

Note: Removing query strings from files is a performance recommendation that was deprecated a long time ago. SO needs to be updated in several areas to reflect this.

Details: Query Strings Deprecated

Details:

Thank you.

I’ve implemented your pagination extension and it works for my site (almost) perfectly. My site is bilingual, using WPML, which uses a query string ?lang=fr to denote the French version of any particular page in the URL. On the English version of the page, there is no query string so the pagination works properly. However, the existing query string on the French version of the page renders the pagination non-functional – it stays stuck on page 1.

I can see what is happening and how the dps query string needs to be attached to existing query string in order to make it work… joining it with an ampersand the language parameter (e.g. ?lang=fr&dps_paged_7=2)… indeed manually doing this in the URL gives me page 2 of the page I’m on. But I wouldn’t know how to modify the source code of the pagination extension to achieve this.

Appreciate your advice.

Many thanks
Trevor

I’m not really sure whether to exclude:
1) the entire page
2) Only “ppc” variable

I have different content on that page according to the ppc numeric value. I thought I tried both points but I still have to clear page cache to see the updated content on the page.

Thank you for claryfin how to exclude the whole page or the query strings

will you include ?v= soon?

Another thing I’d like to know is how Hummingbird handles the referrer query strings like fbclid/gclid parameters. Hummingbird should serve the cached page when these types of query strings are found, if not, visitors from social media sites will not get cache benefits.

WP-Optimize should understand the common query strings and serve the cache files in this case, as all good cache plugins do. Can you please add this in the next update?

I can’t seem to find this answer online.

I’m sending UTM params as a query strings for all outgoing URLS from an android app. The query string shows up on pages & categories but not on blogposts.

My question is does WordPress exclude query strings for blogposts?

Everything online talks about categories and pages but says noting about posts.

Thanks!