Combine CSS is now safe for Elementor\/page-builder sites (relative font and image paths are rewritten correctly). Recommended if you want to cut the number of CSS requests.<\/p>","1.0.2":"
Important fix: JavaScript minification could break theme scripts and leave a loading\/preloader screen spinning so the page never rendered. Update strongly recommended.<\/p>","1.0.1":"
Fixes "cleared cache but still see the old page" (HTML is no longer over-cached by browsers) and lazy loading that could hide images\/videos. Adds automatic image compression with a bulk tool, makes pages faster, encrypts your API keys, and turns the toolbar Boost Cache button into an instant in-place clear. Recommended for all users.<\/p>","1.0.0":"
Initial public release. No upgrade steps required.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3559990,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3559990,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3559990,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3559990,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1","1.0.2","1.0.3","1.0.4","1.0.5","1.0.6","1.0.7","1.0.8","1.0.9","1.1.0","1.1.1","1.1.3","1.1.4","1.1.5","1.1.7","1.1.8","1.1.9","1.2.0","1.2.1"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Dashboard -- live cache statistics, feature status overview, and one-click cache clear.","2":"Page Cache settings -- configure cache lifetime, exclusions, and mobile cache separation.","3":"File Optimization -- HTML, CSS, and JS minification and combining controls.","4":"Media settings -- lazy loading, WebP\/AVIF serving, and video facade options.","5":"CDN settings -- Cloudflare and BunnyCDN API integration configuration.","6":"Database Optimizer -- one-click cleanup for revisions, transients, and orphaned data."}},"plugin_section":[],"plugin_tags":[146,144,187,247,794],"plugin_category":[52,54],"plugin_contributors":[246295],"plugin_business_model":[],"class_list":["post-295388","plugin","type-plugin","status-publish","hentry","plugin_tags-cache","plugin_tags-caching","plugin_tags-optimization","plugin_tags-performance","plugin_tags-speed","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-basecloud","plugin_committers-basecloud"],"banners":{"banner":"https:\/\/ps.w.org\/basecloud-boost\/assets\/banner-772x250.png?rev=3559990","banner_2x":"https:\/\/ps.w.org\/basecloud-boost\/assets\/banner-1544x500.png?rev=3559990","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/basecloud-boost\/assets\/icon-128x128.png?rev=3559990","icon_2x":"https:\/\/ps.w.org\/basecloud-boost\/assets\/icon-256x256.png?rev=3559990","generated":false},"screenshots":[],"raw_content":"\n
BaseCloud Boost<\/strong> is a professional-grade WordPress performance plugin that dramatically speeds up your website through intelligent full-page caching, asset optimization, and smart cache management.<\/p>\n\n Page Cache<\/strong><\/p>\n\n Asset Optimization<\/strong><\/p>\n\n Media Optimization<\/strong><\/p>\n\n Cache Preloader<\/strong><\/p>\n\n CDN Integration<\/strong><\/p>\n\n Database Optimization<\/strong><\/p>\n\n Security Headers<\/strong><\/p>\n\n Developer-Friendly<\/strong><\/p>\n\n BaseCloud Boost connects to the following external services only when you explicitly configure them<\/strong> in the plugin settings. No data is sent to any third-party service by default.<\/p>\n\n If you enable Cloudflare CDN integration and provide a Zone ID and API Token, the plugin calls the Cloudflare API to purge cached content whenever your local cache is cleared.<\/p>\n\n If you enable BunnyCDN integration and provide an API Key and Pull Zone ID, the plugin calls the BunnyCDN API to purge cached content whenever your local cache is cleared.<\/p>\n\n If you configure a webhook URL in the plugin settings, BaseCloud Boost will POST a JSON payload containing anonymous performance metrics to that URL on a daily cron schedule.<\/p>\n\n If you enter a PageSpeed Insights API key in the Lighthouse settings, the plugin calls Google's PageSpeed Insights API to run automated Lighthouse audits for your site.<\/p>\n\n If a page contains a Vimeo video facade, the plugin's frontend JavaScript fetches the video thumbnail from the Vimeo public oEmbed API. This happens in the visitor's browser, not on the server.<\/p>\n\n When the Resource Hints module is enabled, the plugin outputs All remote requests originating from the plugin server-side use WordPress's built-in wp_remote_post() \/ wp_remote_get() functions and respect your server's SSL configuration.<\/p>\n\n\n Yes. Cart, checkout, and My Account pages are automatically excluded from caching. Active WooCommerce cart session cookies bypass the cache transparently.<\/p><\/dd>\n Yes. BaseCloud Boost supports WordPress Multisite with per-site cache directories.<\/p><\/dd>\n Yes. BaseCloud Boost includes Cloudflare and BunnyCDN API integrations. When you purge the local page cache, the plugin automatically purges the corresponding edge cache too.<\/p><\/dd>\n Running multiple full-page caching plugins simultaneously is not recommended and can produce unexpected results. BaseCloud Boost detects and warns you about other active caching plugins on the Dashboard.<\/p><\/dd>\n Deactivate the plugin from the Plugins screen. This automatically removes the advanced-cache.php drop-in and disables WP_CACHE, restoring your site to its previous state.<\/p><\/dd>\n Yes. On activation it sets Defer\/Delay JS: keep the whole Elementor chain together so headers and menus work<\/strong><\/p>\n\n More robust CSS minification + safer Async CSS and JS optimization on page-builder sites<\/strong><\/p>\n\n Dashboard: honest cache status when a reverse proxy is in front<\/strong><\/p>\n\n Combine CSS now also folds stylesheets printed in the Cloudways (managed Varnish) support + reverse-proxy bypass cookie<\/strong><\/p>\n\n Fixed: Delay\/Defer JS broke Elementor menus & widgets even after scripts loaded (no more excluding the whole Elementor stack)<\/strong><\/p>\n\n Fixed: Delay JS made the first click on menus\/buttons do nothing (dropdowns appeared broken)<\/strong><\/p>\n\n Fixed: Critical CSS was corrupted on save (broke hero\/background images)<\/strong><\/p>\n\n Faster LCP on page-builder sites: CSS background images now go through WebP + CDN, and the hero image is preloaded<\/strong><\/p>\n\n Font display + safer Critical CSS<\/strong><\/p>\n\n Combine CSS & Async CSS now work when a CDN is enabled (major mobile fix)<\/strong><\/p>\n\n WooCommerce: fixed \"ghost products\" added to the cart + safer real-time cart on cached pages<\/strong><\/p>\n\n Order-safe JavaScript engine \u2014 fixes broken sliders\/menus and unlocks a big PageSpeed gain<\/strong><\/p>\n\n Asynchronous CSS delivery \u2014 the mobile First Contentful Paint fix<\/strong><\/p>\n\n Faster Largest Contentful Paint + one-click PageSpeed setup<\/strong><\/p>\n\n Two features that silently didn't work now do<\/strong><\/p>\n\nCore Features<\/h4>\n\n
\n
\n
\n
\n
\n
\n
\n
\n
External Services<\/h3>\n\n
Cloudflare Cache Purge API (Optional)<\/h4>\n\n
\n
BunnyCDN Cache Purge API (Optional)<\/h4>\n\n
\n
Performance Metrics Webhook (Optional)<\/h4>\n\n
\n
Google PageSpeed Insights API (Optional)<\/h4>\n\n
\n
Vimeo oEmbed API (Conditional)<\/h4>\n\n
\n
Google Tag Manager \/ Google Fonts Preconnect Hints (Conditional)<\/h4>\n\n
<link rel=\"preconnect\"><\/code> and <link rel=\"dns-prefetch\"><\/code> hints for common third-party origins (Google Tag Manager, Google Analytics, Google Fonts, jsDelivr\/cdnjs). These are passive hints that tell the browser to pre-establish connections \u2014 no data is sent by the plugin itself.<\/p>\n\n\n
\n
basecloud-boost<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n\n
Does BaseCloud Boost work with WooCommerce?<\/h3><\/dt>\n
Is it compatible with WordPress Multisite?<\/h3><\/dt>\n
Can I use it with Cloudflare or BunnyCDN?<\/h3><\/dt>\n
Will it conflict with other caching plugins?<\/h3><\/dt>\n
What if my site breaks after activating the plugin?<\/h3><\/dt>\n
Does BaseCloud Boost modify wp-config.php?<\/h3><\/dt>\n
define( 'WP_CACHE', true )<\/code> in wp-config.php<\/code> so WordPress loads the advanced-cache.php<\/code> drop-in. On deactivation this line is removed. The change is minimal and clearly labelled so it is easy to identify.<\/p><\/dd>\n\n<\/dl>\n\n\n1.2.1<\/h4>\n\n
\n
elementorFrontendConfig<\/code>, ElementorProFrontendConfig<\/code>), the js-cookie<\/code> (Cookies<\/code>) dependency, or the bundled libraries under assets\/lib\/<\/code> (SmartMenus, sticky header, Swiper). With those delayed, the Elementor scripts ran before their config\/libraries existed and threw \"not defined\" errors, so menus, sticky headers and sliders never initialised. The built-in exclusion list now covers the entire Elementor + Elementor Pro footprint (scripts, inline configs, and lib\/<\/code> helpers) plus js-cookie<\/code>, so they load together and initialise correctly \u2014 while analytics, tag managers, chat, forms and WooCommerce scripts are still deferred\/delayed. Still overridable via BCBOOST_default_js_excludes<\/code>.<\/li>\n<\/ul>\n\n1.2.0<\/h4>\n\n
\n
\/* inherit Elementor's font *\/<\/code> \u2014 the minifier mistook that quote for the start of a CSS string and swallowed everything up to the next quote, often hundreds of lines away. The affected CSS (including custom form styling) was then dropped, making elements fall back to their default appearance. Comments and strings are now parsed together in a single pass, so a quote inside a comment can never start a string, and a comment sequence inside a string is never stripped. This also replaces an older comment-stripping pattern that could be slow on very large stylesheets.<\/li>\nBCBOOST_default_js_excludes<\/code>.<\/li>\n<\/ul>\n\n1.1.9<\/h4>\n\n
\n
1.1.8<\/h4>\n\n
<body><\/code> (Elementor\/Astra\/Gravity Forms)<\/strong><\/p>\n\n\n
<body><\/code> are now combined too.<\/strong> Combine CSS only folded stylesheets in the <head><\/code>, but Elementor, Astra and Gravity Forms print widget\/form CSS in the body, where it stayed as many separate render-blocking requests \u2014 adding network latency and, because that CSS styles above-the-fold elements (the nav menu, a contact form), causing layout shifts when it loaded after the content had already painted. Boost now folds those same-origin body stylesheets into a single bundle placed ahead of the content they style. It is intentionally kept render-blocking (not async, unlike the head bundle) precisely because it styles above-the-fold elements \u2014 so the menu and form are styled before first paint instead of flashing\/reflowing. Fewer requests and steadier layout (CLS) on page-builder sites.<\/li>\n<\/ul>\n\n1.1.7<\/h4>\n\n
\n
URLPURGE<\/code> for a single URL and a PURGE<\/code> to \/?purgeall<\/code> for the whole zone, sent to the proxy front-end (defaults to 127.0.0.1:8080<\/code>). Purge requests to internal proxy ports are correctly sent over HTTP.<\/li>\nbcboost-nocache<\/code> bypass cookie.<\/strong> Boost now sets this cookie for visitors who must always get a fresh page (logged in, or with an active WooCommerce cart) and clears it once they're anonymous again \u2014 emitting the cookie only on that transition so normal anonymous pages stay cacheable. Add bcboost-nocache<\/code> to your reverse proxy's excluded-cookies list (on Cloudways: Application \u2192 Varnish Settings \u2192 Excluded Cookies<\/em>) so the proxy bypasses its cache for those visitors. Boost's own page cache honours the same cookie.<\/li>\n<\/ul>\n\n1.1.6<\/h4>\n\n
\n
ready<\/code> until every delayed script has run.<\/strong> Libraries like Elementor self-initialise on jQuery ready the instant their script executes. Because the loader runs delayed scripts one at a time, Elementor would initialise before<\/em> later scripts (Elementor Pro's element handlers, SmartMenus, etc.) had registered \u2014 so dropdown menus and some widgets never bound their behaviour and appeared dead, even once everything had loaded. Boost now pauses jQuery ready the moment jQuery is defined and releases it only after the whole queue drains, so all components initialise together exactly as on a normal page load. This removes the need to exclude jQuery\/Elementor from Delay JS to keep menus working \u2014 keeping the full Total-Blocking-Time benefit on Elementor sites.<\/li>\n<\/ul>\n\n1.1.5<\/h4>\n\n
\n
1.1.4<\/h4>\n\n
\n
background-image: url(\"\u2026\")<\/code> was saved as url(\\\"\u2026\\\")<\/code>. That is invalid CSS, so any rule relying on a quoted value \u2014 most visibly above-the-fold section\/hero background images \u2014 silently failed to render once Critical CSS was enabled. Boost now unslashes the submitted settings before saving (the standard WordPress behaviour), preserving quotes and valid CSS escape sequences. If you enabled Critical CSS on 1.1.3 and a background went missing, re-save your settings on 1.1.4 and clear the cache.<\/li>\n<\/ul>\n\n1.1.3<\/h4>\n\n
\n
background-image<\/code> files are now served as WebP\/AVIF and from your CDN.<\/strong> Boost already rewrote <img><\/code> tags to modern formats and to the CDN host, but section\/hero backgrounds set in CSS (the bulk of Elementor, Divi, Bricks, etc. layouts) were missed \u2014 they stayed as full-size origin JPG\/PNGs baked into the combined stylesheet. Boost now rewrites those url()<\/code> targets to the WebP\/AVIF copy when one exists and to your CDN hostname, exactly as it does for images in the markup. On hero-heavy pages this can cut hundreds of KB off the single most important image. (Requires Combine CSS; clear the Boost cache after updating so the bundle is rebuilt.)<\/li>\nfetchpriority=\"high\"<\/code>.<\/strong> A section background lives inside the CSS, so the browser cannot discover it until the stylesheet has downloaded and parsed \u2014 a major Largest-Contentful-Paint delay on page-builder sites. Boost now detects the first full-width section that carries a background image and adds a high-priority <link rel=\"preload\" as=\"image\"><\/code> for it in the <head><\/code>, so it loads in parallel with the CSS instead of after it. Fully automatic, falls back to no preload when no hero is found, and can be turned off with the Preload LCP image<\/em> option.<\/li>\n<\/ul>\n\n1.1.2<\/h4>\n\n
\n
font-display: swap<\/code> is now applied to fonts inside your stylesheets.<\/strong> Boost already added swap to Google Fonts links and inline @font-face<\/code> blocks, but icon-font packs (Themify, Linearicons, ElementsKit, Font Awesome, \u2026) declare their @font-face<\/code> inside external stylesheets, where it was untouched. Boost now injects font-display: swap<\/code> into those @font-face<\/code> rules while minifying\/combining CSS, so text and icons stay visible during font load (the \"Font display\" PageSpeed item). Governed by the existing Optimize Google Fonts<\/em> toggle.<\/li>\n%xx<\/code> URL-encoded sequence, which silently broke url()<\/code> values (such as inline SVG data URIs) in pasted critical CSS. It now uses CSS-safe sanitisation that removes HTML tags but preserves valid CSS.<\/li>\n<\/ul>\n\n1.1.1<\/h4>\n\n
\n
yourzone.b-cdn.net<\/code>) before Boost folds the page's stylesheets. Boost only recognised origin URLs, so it treated every CDN-hosted stylesheet as \"external\" and skipped it \u2014 leaving the whole page's CSS render-blocking even with Combine CSS + Async CSS (or the Optimize for PageSpeed<\/em> preset) enabled. On a CSS-heavy Elementor site that left dozens of stylesheets blocking first paint and capped the mobile PageSpeed score. Boost now maps CDN asset URLs back to their local files, so all same-origin stylesheets are combined into one bundle and that bundle is delivered asynchronously \u2014 and the bundle itself is served from the CDN. This is the single biggest mobile First-Contentful-Paint \/ Largest-Contentful-Paint fix for sites running BunnyCDN. After updating, clear the Boost cache (and purge your BunnyCDN pull zone) so pages are rebuilt.<\/li>\n<\/ul>\n\n\n
?add-to-cart=ID<\/code> URLs marked rel=\"nofollow\"<\/code>. Loading one actually runs the action, so simply hovering or tapping near a product button could add it to the cart. Both engines now skip every rel=\"nofollow\"<\/code> link and any URL carrying a cart\/AJAX\/nonce action parameter (add-to-cart<\/code>, remove_item<\/code>, undo_item<\/code>, wc-ajax<\/code>, add_to_wishlist<\/code>, _wpnonce<\/code>), as well as the cart\/checkout\/my-account pages. Add-to-cart, remove and quantity changes now only happen when the shopper actually clicks.<\/li>\n1.1.0<\/h4>\n\n
\n
defer<\/code> (or the delay marker) to enqueued<\/em> script files, but left the inline initializers a theme or page-builder hard-codes in the page running during parsing \u2014 before the libraries they call had loaded. On sliders, popups and many WPBakery\/ThemeForest themes that meant \u2026 is not a function<\/code> errors and broken layouts. Boost now treats inline and external scripts as one ordered unit: every eligible script is run through a single loader that executes them strictly in their original order, waiting for each external file to finish before the next. Inline initializers (RevSlider, WPBakery, theme setup) and a script's localized config keep working exactly as the theme intended.<\/li>\nDOMContentLoaded<\/code> and load<\/code> events so everything still initializes. Use Delay JS Exclusions<\/em> to keep specific scripts (analytics, chat, etc.) running immediately, or add data-no-delay<\/code> \/ data-cfasync=\"false\"<\/code> to a tag to opt it out.<\/li>\n<noscript><\/code> fallback) instead of staying render-blocking.<\/li>\n<\/ul>\n\n1.0.9<\/h4>\n\n
\n
media=\"print\"<\/code> + onload swap, with a <noscript><\/code> fallback). The theme's inline above-the-fold CSS paints immediately and the bundle applies as soon as it arrives \u2014 and because the stylesheet is no longer hogging the connection, the LCP image can start downloading sooner too. This is the single biggest lever for mobile First Contentful Paint \/ Largest Contentful Paint on heavy Elementor\/Divi sites. Enable both under File Optimization. (When Combine CSS is off, Async CSS continues to load each stylesheet asynchronously as before.)<\/li>\n<\/ul>\n\n1.0.8<\/h4>\n\n
\n
fetchpriority=\"high\"<\/code> hint is wasted on the placeholder. Boost now detects the LCP\/above-the-fold image, restores its real source immediately (from the usual data-src<\/code> \/ data-orig-src<\/code> \/ data-srcset<\/code> attributes), removes the lazy-load hooks so it can't be hidden again, and preloads it \u2014 using the responsive imagesrcset<\/code>\/imagesizes<\/code> set when one is present so the browser fetches the exact size it will display. The hero starts downloading right away instead of after the page's JavaScript has executed.<\/li>\n1.0.7<\/h4>\n\n
\n