Why Remove query strings from static resources?

  • Resolved funsail

    (@funsail)


    11 years, 2 months ago

    Every page checker recommends you to “Remove query strings from static resources”

    Why does WP like to add versions to everything?
    eg
    /wp-content/themes/mtyem/css/autoinclude/common.css?ver=4.1.1

    That ver=4.1.1 is from WP. The theme doesn’t belong to WP so I have no idea why WP adds stuff to destroy speed on our sites.

    Is there a good reason for this?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Jon (Kenshino)

    (@kenshino)

    Lord Jon

    11 years, 2 months ago

    It doesn’t affect speed. It’s simply a version marker. In actual fact, it doesn’t even query by version no.

    Besides, the version maker can be removed or altered to be more accurate (eg version 2.0 of mtyem theme’s css).

    Your Theme designer/developer should have just added a more appropriate version no.

    Cheers!

    mjassen (mjjojo)

    (@mjjojo)

    11 years, 2 months ago

    Hi! I know this thread is marked “resolved” however I didn’t see the main question answered, so I wanted to follow-up with one “good reason” to do this in web development — is to avoid browser cache issues.

    For example if the developer updates the .css file but its filename remains the same, then the browser still uses the old cached version. From experience I can say that from a user perspective this can make it seem like the web app is broken/unusable! So in theory by updating the filename of the .css file to have the new version number it would tell the web browser to re-cache the file and use the new file.

    To try to find out more about this, I did an internet search for something like:
    auto-versioning to avoid image cache issues

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

The topic ‘Why Remove query strings from static resources?’ is closed to new replies.