WP Remove Query Strings From Static Resources

As it's name, it will remove query string from static resources. Static resources are JavaScript, CSS files. It improves speed of WordPress website. And also it improves speed score in website testing tools like Pingdom, GTmetrix, PageSpeed and YSlow. About Query Strings Benefits of removing query strings It is a part of search engine optimization. So it will improve ranking of your website in search engines. And also it will improve speed score in website testing tools. it improves performance of your website and bring more website visitors.

There are 3 different ways to install any WordPress plugin including WP Remove Query Strings From Static Resources. Simplest: Using WordPress Dashboard

1. Open Dashboard of your WordPress website and then add new plugin page here: Dashboard > Plugins > Add New.
2. Now search for 'WP Remove Query Strings From Static Resources'.
3. Click 'Install Now'
4. Activate the plugin on the Plugin dashboard

Uploading on Dashboard

1. Download plugin zip file from: https://wordpress.org/plugins/wp-remove-query-strings-from-static-resources/
2. Now open Dashboard and then add new plugin page here: Dashboard > Plugins > Add New.
3. Now click on 'Upload Plugin' button.
4. Click on 'Browse...' to select downloaded zip file. Now simply install and activate it.

Uploading using FTP

1. Download plugin zip file from: https://wordpress.org/plugins/wp-remove-query-strings-from-static-resources/
2. Extract this zip file to find folder 'wp-remove-query-strings-from-static-resources'
3. Now upload 'wp-remove-query-strings-from-static-resources' folder inside plugins directory here: '--WP-ROOT--/wp-content/plugins/'
4. Now open Dashboard and then plugins page. Find this plugin and activate it.

1.8

• Remove additional class

1.7

• Added additional class

1.6

• Tested for WP 6.6

1.5

• Tested for WP 6.3

1.4

• Compatibility WP 6.0

1.3

• 23 Feb, 2019
• Text improved
• Increase Version

1.2

• 3 July, 2017
• Code improved

1.1

• 3 July, 2017
• Compatibility issue

1.0

• 29 June, 2017
• First Release