BaseCloud Boost vs SQLite Object Cache

BaseCloud Boost is a professional-grade WordPress performance plugin that dramatically speeds up your website through intelligent full-page caching, asset optimization, and smart cache management. Core Features Page Cache Full-page HTML caching that bypasses WordPress and PHP entirely for maximum throughput GZIP and Brotli compression variants stored alongside each cached page Smart cache invalidation on post updates, comment submissions, and taxonomy changes Configurable cache lifetime (default: 7 days) Separate mobile device cache for responsive-aware caching Cache exclusion by URL pattern or cookie name Asset Optimization HTML, CSS, and JavaScript minification CSS and JS file combining to reduce HTTP requests JavaScript deferral for faster first paint Critical CSS extraction and inline injection Remove query strings from static asset URLs for better CDN hit rates Async-load non-critical Google Fonts with font-display=swap Media Optimization Reliable native lazy loading for images, iframes, and videos — defers off-screen media without ever hiding it, so images always appear On-the-fly image compression — generates high-quality WebP copies of your images on upload, plus a one-click Bulk Compress tool for your existing media library Quality-preserving compression — originals are never altered; WebP copies are created alongside them at a tunable visually-lossless quality WebP and AVIF serving — automatically serves the next-gen format when available Video facade for YouTube and Vimeo — replaces iframes with click-to-play thumbnails preload=”none” applied to video tags for faster page loads Cache Preloader Automatic sitemap-based URL discovery Background batch processing to keep the cache warm Real-time progress tracking in the admin dashboard CDN Integration Generic CDN hostname rewriting for any CDN provider Cloudflare API cache purging — automatically clears Cloudflare edge cache on purge BunnyCDN API cache purging — mirrors local purge events to your Pull Zone Database Optimization Post revision cleanup Auto-draft and trashed post/comment removal Expired transient removal Orphaned postmeta cleanup Table optimization (OPTIMIZE TABLE) Security Headers X-Content-Type-Options, X-Frame-Options, Referrer-Policy Permissions-Policy (FLoC/Topics API opt-out) Strict-Transport-Security (HSTS) for HTTPS sites Developer-Friendly Full hook API: filter cache behaviour, modify HTML before write, extend CDN purge logic WP-CLI commands for cache management PSR-4 autoloaded class architecture External Services BaseCloud Boost connects to the following external services only when you explicitly configure them in the plugin settings. No data is sent to any third-party service by default. Cloudflare Cache Purge API (Optional) 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. Service: Cloudflare, Inc. What it is used for: Purging edge-cached pages so visitors see fresh content after a cache clear. When data is sent: Only when you trigger a cache purge (manually, on post save, or via plugin action). Data sent: List of URLs to purge and your Cloudflare Zone ID (via your API token). API endpoint: https://api.cloudflare.com/client/v4/zones/{zone_id}/purge_cache Terms of Service: https://www.cloudflare.com/terms/ Privacy Policy: https://www.cloudflare.com/privacypolicy/ BunnyCDN Cache Purge API (Optional) 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. Service: BunnyWay d.o.o. (BunnyCDN) What it is used for: Purging Pull Zone edge cache so visitors receive fresh content. When data is sent: Only when you trigger a cache purge. Data sent: URLs to purge and your API key. API endpoints: https://api.bunny.net/purge and https://api.bunny.net/pullzone/{id}/purgeCache Terms of Service: https://bunny.net/tos/ Privacy Policy: https://bunny.net/privacy/ Performance Metrics Webhook (Optional) 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. Service: Custom endpoint configured by you. What it is used for: Sending performance data to an external monitoring or reporting system. When data is sent: Once per day via a scheduled cron event, and when you manually send a test from the admin panel. Data sent: Cache hit rate, cache size, bytes saved (HTML/CSS/JS), last purge time, plugin version, site URL, and site name. No user data or passwords are included. Endpoint: Your custom URL — you are responsible for its security and privacy compliance. Google PageSpeed Insights API (Optional) 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. Service: Google LLC (PageSpeed Insights) What it is used for: Running automated Lighthouse performance audits (Performance, Accessibility, Best Practices, SEO scores). When data is sent: When you manually trigger an audit from the Lighthouse settings page, or on the scheduled Lighthouse cron (if enabled). Data sent: Your site URL and your API key. API endpoint: https://www.googleapis.com/pagespeedonline/v5/runPagespeed Terms of Service: https://developers.google.com/terms Privacy Policy: https://policies.google.com/privacy Vimeo oEmbed API (Conditional) 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. Service: Vimeo, Inc. What it is used for: Retrieving the video thumbnail image to display in the click-to-play facade. When data is sent: When a page containing a Vimeo video facade is viewed by a visitor. Data sent: The Vimeo video ID (no user data or authentication is required). API endpoint: https://vimeo.com/api/v2/video/{id}.json Terms of Service: https://vimeo.com/terms Privacy Policy: https://vimeo.com/privacy Google Tag Manager / Google Fonts Preconnect Hints (Conditional) When the Resource Hints module is enabled, the plugin outputs and 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 — no data is sent by the plugin itself. Service: Various (Google LLC, Cloudflare, Inc.) What it is used for: Reducing connection latency for third-party resources already loaded by your theme or other plugins. When data is sent: The browser (not the plugin) initiates the connection. No plugin data is transmitted. Terms of Service / Privacy: Governed by the respective third-party services. 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.

A persistent object cache helps your site perform well. This one uses the widely available SQLite3 extension, and optionally the igbinary and APCu extensions to php. Many hosting services offer those extensions, and they are easy to install on a server you control. What is this about? It’s about making your site’s web server perform better. An object cache does that by reducing the workload on your MariaDB or MySQL database. This is not a page cache; these persistent objects go into a different kind of cache. These objects aren’t chunks of web pages ready for people to view in their browsers, they are data objects for use by the WordPress software. Caches are ubiquitous in computing, and WordPress has its own caching subsystem. Caches contain short-term copies of the results of expensive database lookups or computations, and allow software to use the copy rather than repeating the expensive operation. This plugin (like other object-caching plugins) extends WordPress’s caching subsystem to save those short-term copies from page view to page view. WordPress’s cache happens to be a memoization cache. Without a persistent object cache, every WordPress page view must use your MariaDB or MySQL database server to retrieve everything about your site. When a user requests a page, WordPress starts from scratch and loads everything it needs from your database server. Only then can it deliver content to your user. With a persistent object cache, WordPress immediately loads much of the information it needs. This lightens the load on your database server and delivers content to your users faster. Who should use this? If your site runs on a single web server machine, and that server provides the SQLite3 and igbinary extensions to php, this plugin will almost certainly make your site work faster. And if that server provides the APCu extension, this plugin uses it too. Some hosting providers offer redis cache servers. If your provider offers redis, it may be a good choice. You can use it via the Redis Object Cache plugin. Sites using redis have one SQL database and another non-SQL storage server: redis. Other hosting providers offer memcached, which has the Memcached Object Cache plugin. And some large multipurpose cache plugins, such as the LiteSpeed Cache, also offer object caching based on one of those cache server software packages. The cache-server approach to object caching comes into its own when you have multiple load-balanced web server machines handling your site. SQLite doesn’t work correctly in a multiple-web-server environment. But, for single-server site configurations, SQLite, possibly assisted by APCu, performs well. And the vast majority of sites are single-server. APCu APCu is an in-memory storage medium. It lets php programs, like WordPress, store data in shared memory so it’s very fast to retrieve when needed. If APCu is available on your host server, you can configure this plugin to use it. It reduces the typical cache lookup time to one-fifth or less of the SQLite lookup time, which is itself a few tens of microseconds. Performance counts, especially on busy web sites. Please look at Installation to learn how to configure this plugin to use APCu. The plugin works fast without it, and faster with it. WP-CLI: Even if APCu is in use, caching with SQLite is necessary when your web site uses WP-CLI, because WP-CLI programs do not have access to the APCu cache. This plugin writes all cached data both to APCu and to SQLite and makes sure the two are synchronized. WP-CLI You can control this plugin via WP-CLI once you activate it. Please type this command into your shell for details. wp help sqlite-object-cache Credits Thanks to Till Krüss. His Redis Object Cache plugin serves as a model for this one. And thanks to Ari Stathopoulos and Jonny Harris for reviewing this. Props to Matt Jones for finding and fixing a bug that appeared on a heavily loaded system. Thanks to Massimo Villa for testing help, and to nickchomey for a comprehensive code review. All defects are, of course, entirely the author’s responsibility. And thanks to Jetbrains for the use of their software development tools, especially PhpStorm. It’s hard to imagine how a plugin like this one could be developed without PhpStorm’s tools for exploring epic code bases like WordPress’s. How can I learn more about making my WordPress site more efficient? We offer several plugins to help with your site’s database efficiency. You can read about them here.