Corrects 1.4.0: the new Used CSS engine was switched on for everyone before it had been tested inside a live WordPress site. This release makes it opt-in and switches it off for you if you updated to 1.4.0, clearing the cache once. Re-enabling it yourself sticks. Recommended for anyone on 1.4.0.<\/p>","1.4.0":"
Major CSS release. Boost now removes the style rules, font alphabets and stylesheets a page cannot use, and stops text jumping when your fonts load \u2014 measured on live sites, this removes 24-73% of the CSS that delays the first paint. Used CSS is on after updating; everything it removes is still loaded in the background, so a mistake shows up as a late style rather than a broken layout. Clear the cache after updating, check your site, and if anything looks wrong switch Used CSS off under File Optimization.<\/p>","1.3.6":"
New built-in Critical CSS generator (Beta, opt-in): create per-template above-the-fold CSS in one click \u2014 no external tooling \u2014 then choose yourself whether to enable Critical CSS inlining and Async CSS. Off by default; nothing changes until you switch it on.<\/p>","1.3.5":"
Mobile speed release: hero image downloads start sooner (auto-preconnect), above-the-fold images are never lazy-loaded, lazy images download at their true rendered size, and icon fonts no longer flash placeholder glyphs. Plus a refreshed admin look.<\/p>","1.3.4":"
Fixes corrupted WebP\/AVIF conversions (interrupted write or faulty server encoder) being\nserved as broken\/blank images: conversions are now written atomically and must fully decode\nbefore use, with the original image always served as the fallback. After updating, run\n wp bcboost verify-conversions --delete-broken --regenerate (or re-run Bulk Compress) to\nrepair existing conversions, then clear the cache. Update recommended.<\/p>","1.3.3":"
Hero-image detection fixes: images with 4-digit widths (e.g. width="1000") lazy-load again\nand can be the preloaded hero, theme background bands and thumbnails are no longer preloaded\nas the hero, and detection now reads the page's own inline styles. Clear the cache after\nupdating. Update recommended.<\/p>","1.3.2":"
Hotfix: WebP\/AVIF serving could display the wrong image when a separately-uploaded media file shared a filename with an image Boost optimized. Boost now verifies a converted file is a real conversion before serving it. Affected pages self-correct after a cache clear. Update recommended.<\/p>","1.3.1":"
Hotfix for 1.3.0 on Redis\/persistent-object-cache hosts: settings saves could appear not to stick (values were saved in the database but the object cache kept serving old ones). Self-heals on the first wp-admin load after updating. Update recommended.<\/p>","1.0.3":"
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","1.2.2","1.2.3","1.3.0","1.3.1","1.3.2","1.3.3","1.3.4","1.3.5","1.3.6","1.3.7","1.3.8","1.4.0","1.4.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 Used CSS is now opt-in. If you updated to 1.4.0, this switches it back off for you.<\/strong><\/p>\n\n 1.4.0 introduced the Used CSS engine and switched it on for everybody. That was the wrong call and this release corrects it.<\/p>\n\n The engine's analysis was checked thoroughly, but only offline \u2014 against copies of real client pages, never inside a running WordPress site. The parts that touch a live request (finding the stylesheets in the page, swapping in the shortened version, building it after the page is sent) had no testing at all, and there was no library of theme and plugin combinations to justify turning something that rewrites every page's CSS on for everyone by default.<\/p>\n\n Note that the font-swap layout fix introduced in 1.4.0 is delivered as part of the Used CSS bundle, so it is inactive while Used CSS is off. Separating the two is on the list.<\/p>\n\n What happens next:<\/strong> a compatibility test suite across common themes and plugins, with screenshot comparison and scripted interaction, so that switching this on by default is backed by evidence rather than judgement. Until then it stays opt-in.<\/p>\n\n The CSS release: your pages stop waiting for stylesheets they cannot use<\/strong><\/p>\n\n A page cannot show anything until the browser has downloaded and read every stylesheet in its head. Measured across ten live client sites, each one was making phones read between 0.8 MB and 1.9 MB of CSS before a single word could appear \u2014 and between a third and three quarters of it belonged to widgets, icon sets, forms and languages that were nowhere on the page. Not one byte of it was being loaded in the background. That, rather than JavaScript, is why mobile scores stayed low on sites where the cache, the image conversion and the third-party script delay were all working correctly.<\/p>\n\n If something looks wrong<\/strong><\/p>\n\n This is the first release of a new CSS engine. It was built and checked against real client pages, but every site is different. If anything looks off, switch Used CSS<\/strong> off under File Optimization and clear the cache \u2014 the page returns to exactly its previous behaviour immediately. Individual stylesheets can also be excluded there without giving up the benefit elsewhere.<\/p>\n\n Mobile release: Combine CSS actually combines now, self-hosted fonts stop bloating every page, and Boost tells you which optimizations you have left switched off<\/strong><\/p>\n\n Also in this release<\/strong><\/p>\n\n Hotfix: video and iframe embeds render reliably again<\/strong><\/p>\n\n Elementor Speed (opt-in), a redesigned Light\/Dark admin, the Fleet Ops read-only API, and an HTML-freshness correctness fix<\/strong><\/p>\n\n New: a built-in Critical CSS generator (Beta, opt-in) \u2014 the key that unlocks async CSS<\/strong><\/p>\n\n Mobile speed release: the hero image starts downloading sooner, above-the-fold images are never lazy-loaded, lazy images download at their true rendered size, and icon fonts no longer flash placeholder glyphs<\/strong><\/p>\n\n Corrupt WebP\/AVIF conversions can no longer be served: conversions are now written atomically and fully verified before use, and a new repair command fixes existing broken files<\/strong><\/p>\n\n Hero-image detection targets the right image: 4-digit-width images lazy-load again, theme background bands are no longer preloaded, and detection now reads inline styles<\/strong><\/p>\n\n Hotfix: WebP\/AVIF serving no longer picks up unrelated same-name files, and hidden images are no longer treated as the hero<\/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.4.1<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
1.3.9<\/h4>\n\n
\n
style.css?ver=4.2.1<\/code>). Boost looked for a file with that version tag in its name<\/em>, never found one, and quietly skipped the stylesheet \u2014 so on a normal site the combiner merged only the rare stylesheet that happened to carry no version, and everything else still loaded as its own render-blocking request. Measured on a live client site: Combine CSS switched on, and 44 of the page's 47 stylesheets were still arriving individually. Combining now works as described. Please re-test any site where you have Combine CSS enabled<\/strong> \u2014 for the first time it will genuinely merge your stylesheets, which is a large mobile win but also the change most likely to disturb a slider, form or menu. Check the site after updating and clear the cache; if anything looks wrong, switch Combine CSS off. (Minification was never affected \u2014 only combining.)<\/li>\n\n
1.3.8<\/h4>\n\n
\n
preload=\"none\"<\/code>.<\/strong> An autoplay video must start buffering immediately \u2014 its poster is usually the page's LCP. Only passive click-to-play videos are now demoted.<\/li>\n<\/ul>\n\n1.3.7<\/h4>\n\n
\n
post-*.css<\/code> requests per page, an always-loaded eicons<\/code> icon stylesheet, and Font Awesome shims. The new module (File Optimization \u2192 Elementor Speed, master toggle off<\/strong> until you enable it) inlines each page's own Elementor CSS straight into the HTML (identical rules, same position, minus every one of those blocking requests), drops the eicons\/Font Awesome stylesheets only on pages that provably use no icons, lightboxes, popups or carousels (any doubt = the sheet stays), and adds a read-only advisor that flags Elementor settings worth changing (font-display swap, Inline Font Icons, Element Caching alongside a page cache). Elementor's own JavaScript and init order are never touched \u2014 that is exactly what historically breaks sliders and forms \u2014 and the advisor also warns on oversized DOM (Boost will never restructure your markup; the fix belongs in the builder).<\/li>\nbcboost\/v1<\/code> REST API with a revocable, encrypted pairing key and optional signed requests) ships in this release but stays fully dormant \u2014 the API does not register and there is nothing to configure \u2014 until the BaseCloud service goes live in a future update.<\/li>\nmax-age=0, must-revalidate<\/code>, plus logged-in no-store protection) are now sent unconditionally \u2014 the toggle only gates the static-asset caching rules, as it always should have.<\/li>\nregex:<\/code> patterns alongside substrings, so Oxygen's numeric per-page stylesheets are protected exactly \u2014 while its site-wide sheets stay eligible for minify\/combine\/async. An invalid pattern fails closed (the stylesheet stays render-blocking) and is logged: a typo can slow a page, never break one.<\/li>\n1.3.6<\/h4>\n\n
\n
fetchpriority=\"high\"<\/code> \u2014 two \"highest priority\" images then fight for the same critical bandwidth and both paint later. Boost now removes the competing marker (returning those images to normal browser priority, never forcing them low) so the real hero wins the connection.<\/li>\n1.3.5<\/h4>\n\n
\n
fetchpriority=\"low\"<\/code> so the hero keeps the bandwidth.<\/li>\nsizes=\"auto\"<\/code> (the WordPress 6.7 core mechanism, applied by Boost on older WordPress and page-builder markup too): supporting browsers pick the image variant that matches how large the image actually renders instead of a viewport-width guess \u2014 on phones this substantially cuts image bytes and fixes the PageSpeed \"Properly size images\" flag. Older browsers simply ignore it. Toggle under Media \u2192 \"Right-Size Lazy Images\".<\/li>\nswap<\/code> to every<\/em> font, including icon fonts (Font Awesome, Dashicons, Divi\/Elementor icon packs, WooCommerce stars) \u2014 during the swap window the fallback font would paint a meaningless letter or tofu box where each icon belongs, most visibly on slow mobile connections. Icon fonts are now detected (by name and by their private-use-area unicode-range) and get block<\/code> \u2014 briefly invisible, then the correct icon \u2014 while text fonts keep swap<\/code> so real copy is never invisible. Detection matches font family names and file names only, never directory paths, so a text font that merely lives in a theme or plugin folder with an icon-like name is untouched.<\/li>\nuploads\/elementor\/css\/post-*.css<\/code> where detection previously could not see it \u2014 those pages silently got no hero preload. The detector now reads just those local files (never a network fetch, tightly capped) so external-file Elementor heroes are preloaded like everyone else's. Sections with different desktop\/mobile backgrounds are still deliberately skipped rather than guessed.<\/li>\n1.3.4<\/h4>\n\n
\n
WP_DEBUG_LOG<\/code> entry names the offending file once.<\/li>\nWP_DEBUG_LOG<\/code> entry explains this once.<\/li>\nwp bcboost verify-conversions<\/code> repairs existing conversions.<\/strong> The WP-CLI command scans every existing WebP\/AVIF conversion, reports corrupt ones, and with --delete-broken --regenerate<\/code> removes and rebuilds them (batchable via --batch<\/code>). It also cleans up any orphaned temporary files. Safe everywhere: separately-uploaded files that merely share a name with an original (the 1.3.2 protection) and animated WebP files are never touched \u2014 but Boost's own<\/em> conversions that turn out broken are now regenerated instead of being skipped forever.<\/li>\n<\/ul>\n\n1.3.3<\/h4>\n\n
\n
width=\"1000\"<\/code>) being wrongly treated as tracking pixels.<\/strong> The tracking-pixel check matched any width\/height starting<\/em> with 1<\/code>, so full-size content images with widths like 1000 or 1200 were silently excluded from lazy-loading and<\/em> from hero (LCP) prioritisation. These images now lazy-load normally and are eligible to be the preloaded hero again; only genuine 1\u00d71 pixels remain exempt.<\/li>\n--awb-background-image<\/code>) or onto a small thumbnail instead of the real hero. Custom-property declarations are no longer mistaken for inline backgrounds, thumbnails and other insignificant images (logos, icons, thumb<\/code>-named files) are vetoed, and affected pages self-correct on the next cache clear.<\/li>\n<style><\/code> blocks<\/strong> (Elementor-embedded CSS and Critical CSS) to find section background heroes \u2014 it never fetches external stylesheets to do so. It also skips images hidden on mobile (e.g. elementor-hidden-mobile<\/code> wrappers), and when it cannot confidently identify the hero it now emits nothing rather than guessing \u2014 a per-page bcboost_lcp_image<\/code> custom field remains available as the manual override (a WP_DEBUG_LOG<\/code> hint names it when detection stands down).<\/li>\n<\/ul>\n\n1.3.2<\/h4>\n\n