WordPress Speed Booster Pack Plugin post will help you improve the speed, performance of your website and reduce the usage of resources in your server.
Last Updated: April 11, 2021
Latest News: Updated the documentation.
If you want to improve the speed, loading and resource usage in your website then this is the plugin for you. It is very simple to set up and at the same time very powerful. That is why I recommend that you create a backup before you begin setting up the plugin. Also it is very important that you read the documentation before you begin.
Note: I will be slowly updating all the tutorials because of the latest version 4.1.1.
Speed Booster Pack version 4.1.3 Changelog
- Improved: Cloudflare integration improvements.
- Improved: Hosting compatibility improvements.
- Improved: Settings panel improvements.
- Fixed: HTML encoding/decoding issues with the SimpleHtmlDom library.
- Fixed: Changed the placeholder image data URI when lazy loading is active (used to show a broken image icon).
- Fixed: Kinsta compatibility improvements caused some PHP warnings – not anymore.
What you need:
- Speed Booster Pack
- Speed Booster Pack Documentation = (Important: Please read this documentation before you enable any of the options in the plugin.)
Speed Booster Pack Tutorials
- Speed Booster Pack Plugin
- CDN And Proxy
- CSS Optimizations
- Optimize Site Steps
WordPress Speed Booster Pack Plugin
Step 1 ) Go to Speed Booster to set up the plugin and start improving your website speed and performance. The following image displays the plugin admin menu. The list from the menu below allows you to enable, configure and improve your website speed.
Speed Booster Admin Menu
- CDN & Proxy
- CSS Optimizations
Below are some of the settings in Speed Booster Pack you will be able to enable or disable to improve your site speed.
- Enable/Disable Caching = Enables or disables the whole module without resetting its settings.
Cache expiry time = How many hours to expire a cached page (1 or higher). Expired cache files are regenerated automatically.
- Separate mobile cache = Creates separate cache files for mobile and desktop. Useful if you have mobile-specific plugins or themes. Not necessary if you have a responsive theme.
- Exclude URLs = Enter one URL per line to exclude them from caching. Cart and Checkout pages of WooCommerce are always excluded, so you don’t have to set them in here.
- Cached query strings = Enter one query string per line to cache URLs with those query strings.
For example, after adding “foo” to the list, example.com/blog-post/?foo=bar will be cached.
- Enable/Disable Assets = Enables or disables the whole module without resetting its settings.
- Minify HTML = Removes all whitespace characters from the HTML output, minimizing the HTML size.
- Optimize Google Fonts = Combines all Google Fonts URLs into a single URL and optimizes loading of that URL.
- Lazy load media = Defers loading of images, videos and iframes to page onload.
- Lazy load exclusions = Excluding important images at the top of your pages (like your logo and such) is a good idea. One URL per line.
- Preload assets = Enable preloading of the assets specified below. Enter full URLs of the assets you want to preload. One URL per line.
- Enable/Disable Special = Enables or disables the whole module without resetting its settings.
- Enable CDN = Rewrites all asset URLs with the specified CDN domain. Enter the CDN domain without a protocol or a trailing slash; a relative protocol will be automatically added to all changed asset URLs.
- Localize Google Analytics & Google Tag Manager = Searches for Google Analytics or Google Tag Manager scripts (analytics.js, gtag.js or gtm.js) in your page sources, and replaces them with a locally saved script.
- Custom code manager = Code blocks added with this tool can be loaded in the header, the footer and can even be delayed.
- Jetpack: Dequeue the devicepx script = The devicepx-jetpack.js file replaces images served via Jetpack’s Photon CDN with their higher-quality equivalents. If you don’t need this feature, you can dequeue the file and save an extra HTTP request and an extra DNS connection.
- WooCommerce: Disable cart fragments = Dequeues the cart-fragments.js file if the visitor’s cart is empty, preventing an unnecessary and slow AJAX request.
- WooCommerce: Optimize non-WooCommerce pages = Prevents loading of WooCommerce-related scripts and styles on non-WooCommerce pages.
- WooCommerce: Disable password strength meter = Disables the password strength meter for password inputs during a WooCommerce checkout.
Note: Remember to carry out some testing before you save your settings. Sometimes depending on the site setup, plugins, theme and or your server configuration, you will not be able to enable all the options listed above.
Q1 Is it possible to use the plugin for caching, using Cloudflare?
Answer: Unfortunately no. Caching only works when you have full write permissions. Check the following support thread to learn more.
Q2 I am trying to create 2 css and js files to be loaded on each page. Is this possible with your plugin?
Answer: Unfortunately, it’s not something that is on our roadmap for future versions; because Google PageSpeed and similar performance testing/tracking services argue against bundling CSS and JS files. Because websites using HTTP/2 protocols can serve so many assets at once and allow parallel downloading, bundling CSS/JS files became an old, obsolete practice. Check the following support thread to learn more.
Q3 I have come across a number of entries that begin with
sbp_in the database. Are these yours? Are there others?
Answer: The uninstall process of SBP removes the options used by SBP currently. However if you’re an old user, remnants of the old SBP options (before the time we, Optimocha, acquired Speed Booster Pack) you might be stuck with a few lines in options. A few lines of options, even when they’re autoloaded, won’t affect your website performance in any way but feel free to remove them if you want to. Check the following support thread to learn more.
Q4 Why don’t you combine Css and js files?
Answer: With the HTTP/2 protocol which is used by the majority of the websites around the world (source), it’s not necessary to combine assets like CSS and JS.
In some cases, it might even be harmful to speed because the browser wouldn’t be able to download small files in parallel. Downloading a large, 1MB single CSS file takes more time than downloading, say, 10 CSS files that are 1MB in total. Check the following support thread to learn more.
Q5 Why is ExpiresByType default values (css, js, font files) not the same as Google Guidelines and set to 30 days. Can this be extended by default?
Answer: The ExpiresByType values are based on the famous HTML5 Boilerplate: https://github.com/h5bp/html5-boilerplate/blob/master/dist/.htaccess. Check the following support thread to learn more.
I will be updating this tutorial from time to time. Make sure you come back for the latest updates.
If you have any questions please let me know.