Please read the following tips regarding the usage of to avoid any inconveniences later on. This is useful if you haven't used a page speed booster plugin before or you're also using a caching plugin for the page caching feature. If you're already familiar with the plugin or read the explanations below, just mark this area as "read" using the slider button from the bottom of this page.
The core functionality of , as its name suggests, is to help you unload CSS Stylesheets (.css) & JavaScript (.js) files through the CSS & JavaScript load manager wherever they are loading in excess. This has always been the main purpose of this page speed booster plugin.
It's recommended that you take this action first on whatever page you wish to optimize (e.g. homepage), before minification & concatenation of the remaining loaded files (as you will eventually end up with less and smaller optimized files). They are extra features added to the plugin and are meant to further reduce the number of HTTP requests and also get a smaller page size as the minification will help with that.
If you're already using other plugin for minification and concatenation, and you're happy with its configuration and decide to keep it, you can just use for stripping the "fat" and the other plugin such as WP Fastest Cache or Autoptimize will take the remaining files and optimize them. Don't enable minification/concatenation on both and other caching plugin at the same time as this could lead to extra resources loaded and can generate conflicts or even duplicated files that will end up increasing the total page size.
Let's suppose you're optimising the homepage that has a total of 20 CSS/JS files loading and decided that 8 CSS & JavaScript files are not needed there. Once they are prevented from loading (not deleted or altered in any way from their original source, this plugin doesn't do that), the remaining 12 files will be minified/combined (if you have this option enabled) by either , WP Fastest Cache or other plugin you decided to do this and saved into smaller and fewer files. This will end up in a decreased total page size, deferred unused CSS & less HTTP requests resulting in a faster page load and a higher page speed performance score (via tools such as GTMetrix).
As long as you will prevent useless files from loading, then you will for sure have a lighter & faster website. If anything changes in your hosting configuration, the size of your images or any external scripts etc. that you're website is loading, then you could end up with a slower website and that is not dependent on nor any other WordPress performance plugin as there are external things which will never depend entirely on a plugin.
doesn't add any extra files to load in the front-end view that will increase the number of HTTP requests in any way as it will defy its purpose. It's main task is to prevent other files from loading and cleaning up the HTML code. Moreover, by enabling concatenation (if your website is not using the HTTP/2 protocol), you will reduce the number of HTTP requests further. If you're using another plugin that also has an option for minification/concatenation, and you have enabled the feature on both plugins (never do it), or haven't configured something the right way, you could end up with extra CSS/JS loaded that will eventually lead to a poorer page speed score and a slower website.
will never alter (in any way) or delete CSS & JS files from their original source (e.g. plugins, themes). Files created through minification/concatenation are cached and stored in directory.