Beplus Performance Booster vs DietPress

Beplus Performance Booster is a no-bloat performance plugin that gives you fine-grained control over your site’s front-end assets. All features can be toggled independently from a single settings page (Settings > Beplus Performance Booster). All front-end optimisations are bypassed for logged-in administrators so you never accidentally break the admin panel or your own editing experience. Feature summary: JavaScript delay (Simple / Advanced mode) and defer with per-script exclude list JS Release Delay: image-load fallback timer for releasing delayed scripts CSS file and inline minification with cache Remove Unused CSS: per-URL cached stripping of unused CSS rules Non-render-blocking stylesheet loading Lazy load images with IntersectionObserver fallback Remove emoji, wp-embed, Gutenberg CSS, WooCommerce assets on non-shop pages HTML minification and comment stripping Browser cache and gzip/brotli rules via .htaccess Per-page option to disable the cache for specific posts/pages Custom CDN (pull-zone) URL rewriting for static assets Settings Reference Navigate to Settings > Beplus Performance Booster to configure the plugin. ⚡ JavaScript Optimization Delay JS Execution Default: off Delays all non-excluded front-end scripts until the first user interaction (click, scroll, keydown, or touchstart), or until the JS Release Delay timer fires — whichever comes first. Delay Mode — choose how scripts are intercepted: Simple — converts WordPress-enqueued external scripts to text/plain placeholders and replays them on first interaction. Low risk, no event-queue replay. Advanced — output-buffer approach that intercepts every tag on the page (including hardcoded theme scripts and dynamically injected ones) via MutationObserver. Replays DOMContentLoaded and window.load event queues in correct order. Test thoroughly before enabling on production. JS Release Delay (ms) — fallback timer (ms) that releases delayed scripts after above-fold images and fonts finish loading, without requiring user interaction. 0 = disabled — only user interaction releases delayed scripts. Defer Non-Critical JS Default: off Adds the defer attribute to every non-excluded tag so scripts are fetched in parallel and executed after the HTML is parsed. jQuery and jquery-migrate are always protected from deferral. Exclude JS Files Default: empty One URL keyword per line. Any script whose src attribute contains a listed keyword is excluded from both Delay and Defer. Use this to protect scripts that must run immediately (e.g. analytics that need to capture the first page view). Examples: jquery, woocommerce, my-critical-script 🎨 CSS Optimization Minify Inline CSS Default: off Strips block comments (/* … */), collapses redundant whitespace, and removes trailing semicolons from every inline block in . License comments (/*! … */) are preserved. Spaces around + are intentionally kept so calc(100% + 20px) expressions are never broken. Minify CSS Files Default: off Requires: wp-content/uploads/bepluspb-cache/ directory to be writable Minifies every enqueued external CSS file and serves the cached version from wp-content/uploads/bepluspb-cache/. Already-minified *.min.css files and external CDN stylesheets are skipped automatically. Cache files are named using a 12-character content MD5 hash so they self-invalidate whenever the source changes. Non-Render-Blocking CSS Default: off Converts tags to the preload + onload swap pattern: This prevents stylesheets from blocking the initial render. A fallback ensures CSS loads correctly even when JavaScript is disabled. Tip: if you see a flash of unstyled content (FOUC), add your theme’s main stylesheet URL keyword to the Exclude CSS Files list. Exclude CSS Files Default: empty One URL keyword per line. Stylesheets whose href contains a listed keyword are left completely untouched by the Non-Blocking, Inline All CSS, Minify CSS Files, and Remove Unused CSS features. Remove Unused CSS Default: off Requires: wp-content/uploads/bepluspb-cache/ directory to be writable Scans the fully rendered page and strips CSS rules whose selectors never appear in that page’s HTML, caching the trimmed stylesheet per URL. This is a static text match (not a real browser render): the first visit to a URL generates the trimmed file in the background while still serving the original CSS; later visits to the same URL load the trimmed version. Classes added dynamically by JavaScript after page load will not be detected as “used” — add them to the Unused CSS Selector Safelist below. Unused CSS Selector Safelist Default: empty One selector or keyword per line (trailing * wildcard supported). Rules matching these are always kept regardless of whether they were detected as used. Use this for JS-toggled classes (menus, modals, tabs, accordions) and plugin/page-builder dynamic states. Example: .active, .is-open*, .woocommerce-* Unused CSS URL Excludes Default: empty One URL keyword per line. Matching pages never have unused CSS removed. Recommended for checkout/cart and other heavily dynamic pages. 🖼️ Lazy Load Images Enable Lazy Loading Default: off Adds loading="lazy" to qualifying tags found in post content, featured images, widget text, and elements. For browsers that do not support the native loading attribute, a small IntersectionObserver polyfill is injected into wp_footer (activates only when native support is absent). Skip First N Images Default: 1 Images 1 through N are marked loading="eager" instead of loading="lazy". Set this to at least 1 to protect the hero/LCP image from being lazy-loaded, which would hurt Core Web Vitals. Accepts 0–20. Exclude by CSS Class Default: empty Comma-separated CSS class names. Any that has one of these classes loads eagerly (not lazily). Example: hero-image, no-lazy, skip-lazy Exclude by Element ID Default: empty Comma-separated element IDs. Any with a matching id attribute loads eagerly. Example: hero-banner, site-logo Exclude by Filename Default: empty Comma-separated partial filename strings. Any whose src URL contains one of these strings loads eagerly. Example: logo, hero, banner 🗑️ Remove Unused Assets Remove Emoji Scripts Default: off Removes the WordPress emoji detection script, its inline stylesheet, and the s.w.org DNS prefetch hint. Safe to enable if you use real Unicode emoji in your content — browsers display them natively without the WordPress helper. Remove oEmbed / wp-embed Default: off Removes the wp-embed.js script and the oEmbed discovery links added to . Also unregisters the oEmbed REST API endpoint. Disable only if you rely on embedding your WordPress posts inside other websites. Remove Block / Gutenberg CSS Default: off Dequeues wp-block-library, wp-block-library-theme, and global-styles stylesheets on the front-end. Disable if your theme or content depends on Gutenberg block styles. Disable WooCommerce Assets on Non-Shop Pages Default: off Requires: WooCommerce active Dequeues WooCommerce scripts and styles on pages that are unrelated to the shop, cart, checkout, or account. WooCommerce assets are always kept on those pages. 📄 HTML Optimization Minify HTML Output Default: off Collapses redundant whitespace between HTML tags in the full page output. Content inside , , , and tags is always preserved exactly as-is. Remove HTML Comments Default: off Strips HTML comments (e.g. theme generator tags, plugin banners) from the page output. Conditional IE comments are also removed. Remove Inline JS Comments Default: off Removes // single-line and /* … */ block comments from inline blocks in the HTML output. String literals and template literals are never modified. License comments (/*! … */) are preserved. Remove Inline CSS Comments Default: off Removes /* … */ block comments from inline blocks in the HTML output. 🚀 Browser Cache Headers (.htaccess) Enable Browser Caching Default: off Requires: Apache with mod_expires, mod_headers, mod_deflate. .htaccess writable. Injects the following directives into the root .htaccess file inside a clearly labelled block that is never duplicated: Gzip compression (mod_deflate) for HTML, CSS, JS, JSON, SVG, and fonts. Brotli compression (mod_brotli, Apache 2.4.26+) for the same types. Expires headers (mod_expires): 1-year cache for static assets; no-cache for HTML and API responses. Cache-Control headers (mod_headers): max-age=31536000, public, immutable for CSS, JS, images, and fonts. Disabling this option or deactivating the plugin removes the injected block cleanly. 📦 JS File Minification & Cache Minify JS Files Default: off Requires: wp-content/uploads/bepluspb-cache/ directory to be writable Minifies every enqueued JavaScript file using a safe character-by-character comment stripper that correctly handles string literals, template literals, and URL protocol slashes (https://). Already-minified *.min.js files and external CDN scripts are skipped. Cache files use a 12-character content MD5 hash for automatic cache busting. Lines are never joined to avoid breaking JavaScript’s Automatic Semicolon Insertion (ASI) rules. Cache Status Shows how many CSS and JS files are currently stored in the cache directory (wp-content/uploads/bepluspb-cache/). Use the “Clear CSS/JS Cache” button to delete all cached files; they are regenerated on the next page load. The “Beplus Performance Booster” item in the WordPress admin bar (visible to administrators on both the front-end and back-end) shows cache size and file count in a dropdown panel and provides a one-click button to clear the cache. ☁️ CDN Enable CDN Default: off Rewrites matching static-asset URLs on this site to the CDN domain configured below — enqueued CSS/JS, media library images (including responsive srcset), matching URLs inside post content and widgets, and any other matching URL in the rendered page (including root-relative paths written directly into theme or page-builder markup). External URLs and already-CDN URLs are left untouched. Like other front-end optimisations, this is skipped for logged-in administrators. CDN URL Default: empty Your CDN pull-zone domain — for example, the hostname assigned when you add this site as a CDN zone with a provider such as QUIC.cloud (e.g. https://xxxxxxxx.quic.cloud), BunnyCDN, or KeyCDN, or a custom domain CNAME’d to one. This is a generic pull-zone rewriter and works with any CDN provider — it is not an official integration with any of them. File Types Default: css,js,jpg,jpeg,png,gif,webp,avif,svg,ico,woff,woff2,ttf,otf,eot,mp4,webm,pdf Comma-separated file extensions. Only URLs ending in one of these are rewritten to the CDN; everything else (PHP endpoints, REST/AJAX requests, admin URLs) is untouched by design since the matching is extension-based. Exclude from CDN Default: empty One URL keyword per line. URLs containing any of these strings stay on your own domain instead of being rewritten to the CDN. Per-Page Cache Disable (Meta Box) Every post and page edit screen includes a “Beplus Performance Booster” meta box in the sidebar. Checking Disable CSS/JS cache optimizations for this page/post stores the _bepluspb_disable_cache flag in post meta. When set, the Minify CSS Files and Minify JS Files features are bypassed for that specific URL and the original (unminified) files are served instead. Useful for debugging or resolving conflicts on a specific page without disabling minification site-wide. About BePlus This plugin is developed and maintained by BePlus, a WordPress and Shopify development studio with 10+ years of experience building themes and plugins for nonprofits and eCommerce brands. Learn more at beplusthemes.com.

DietPress is a free WordPress speed optimization plugin with a built-in page cache. Page caching, browser caching, GZIP and Brotli compression, deferred JavaScript, critical CSS, image loading attributes, preloading, locally hosted Google Fonts and selective asset loading, all in one plugin and all free. And it goes further than a caching plugin: it also puts WordPress itself on a diet, switching off the features your site never uses. It pairs that with a clean, risk-based interface. Everything is configurable, the optimizations are already on by default, and nothing is hidden behind a paid tier. Activate it and your site is faster, or open the settings and tune every detail. By default WordPress loads functions, services and scripts that most sites do not need. They slow down loading times and consume hosting resources. DietPress lets you trim that fat and apply battle-tested performance tweaks, with a clear description of what each option does and what might break, organized by risk level so you always know what is safe. WHY CHOOSE DIETPRESS Page caching, for free. Serve anonymous visitors a copy stored on disk instead of building the page again. The feature people buy WP Rocket or a NitroPack subscription for, with no licence and no monthly fee. No drop-in, no changes to wp-config.php. Unlike WP Super Cache or W3 Total Cache, DietPress installs no advanced-cache.php and never edits wp-config.php. Switching it off leaves your site exactly as it was, with nothing orphaned behind. It tells you why. Most cache plugins leave you guessing when nothing is cached. DietPress reports its own status, tests itself against your home page, and names the exact reason a page was skipped. WooCommerce-safe by design. Carts, checkout, my account and any visitor carrying a cart cookie always get the live site, so nobody ever sees somebody else’s basket. Diet as well as speed. Where Perfmatters focuses on disabling scripts, DietPress covers that ground and adds page caching, critical CSS, local Google Fonts and a dashboard, admin and email cleanup, in one plugin. Light on your server. No account, no external service, no telemetry, no upsell nags. Everything runs on your own hosting. WHAT THE PAGE CACHE DOES TO YOUR RESPONSE TIME Measured on a WordPress 7.0 install with GeneratePress, WooCommerce and a 76 product catalogue, PHP 8.5, taking the median of 15 requests per URL. Your own hosting will give different figures, but the shape of the result will not change. Server response time, the same pages with the page cache off and on: Home page – 52.7 ms without, 15.1 ms with, 71% faster WooCommerce shop – 45.4 ms without, 14.8 ms with, 67% faster A 110 KB article – 43.0 ms without, 15.1 ms with, 65% faster A 98 KB page – 41.0 ms without, 14.9 ms with, 64% faster A product category – 41.3 ms without, 15.1 ms with, 63% faster The interesting part is not the percentage, it is that the cached figure barely moves. Serving a stored file costs the same whether the page was cheap or expensive to build, so the saving grows with the size of your site rather than with the power of your server. The heaviest page in the test is the one that gained most. It also changes how much traffic your hosting can take at once. In the same test the server went from serving about 40 visits a second to more than 210, five times as many, on exactly the same plan. That is what keeps a small site standing up when one of your posts does well. TWO THINGS IN ONE PLUGIN 1. Performance optimizations (on by default) Automatic Critical CSS inlined in the head (optional experimental deferral of non-critical CSS) JavaScript defer parsing with smart dependency handling Image loading attributes safety net: lazy loading, decoding=async and fetchpriority for images that bypass core Automatic image dimensions for better CLS scores (including picture elements) Resource hints: preconnect and DNS prefetch for common third-party origins Theme stylesheet, critical fonts and logo preloading for a faster LCP Google Fonts display=swap Google Fonts local hosting: serve the fonts your theme uses from your own server, GDPR-friendly with a silent fallback to the Google CDN (opt-in) Selective third-party loading: WooCommerce, Contact Form 7, block library, Slider Revolution, TablePress, Smash Balloon, Formidable Forms and Everest Forms assets only load where they are used (opt-in) RSS feed optimization (cache headers and item limit) Server rules in .htaccess: browser caching with a configurable lifetime for media, for styles and scripts and for fonts, GZIP and Brotli compression, immutable cache headers, CORS for fonts and keep-alive (master switch plus per-feature toggles) Database maintenance: daily expired-transient cleanup and safe query optimizations Page cache: store each page on disk and serve it to anonymous visitors without building it again, with automatic purging, gzip precompression and a status panel that says whether it is working (opt-in, in its own tab) 2. Put WordPress on a diet (risk-based, opt-in) Light (safe for any site): emojis, RSD/WLW tags, shortlinks, self-pingbacks, comment pagination, and more Moderate (evaluate first): oEmbed, jQuery Migrate, Dashicons on the frontend, Global Styles and Duotone, remote block patterns, avatars and Gravatar, comment threading, and more Strict (site-specific): granular RSS feed control, Heartbeat API mode, post revisions and autosave, disable comments, XML sitemap, native lazy loading/fetchpriority, content types, selective loading for WooCommerce, Contact Form 7, block assets, Slider Revolution, TablePress, Smash Balloon, Formidable Forms and Everest Forms, and more Widgets: dashboard widgets (including third-party ones from Yoast, WooCommerce, Elementor, Jetpack, Wordfence, Rank Math, Gravity Forms), classic sidebar widgets, block-editor widgets and the Customizer Emails: silence the automatic emails WordPress sends on its own, grouped by area: auto-update results for core, plugins and themes (plus the new-version notice), comment moderation and new-comment notices, and new user, password and email-change notices, plus toggles for the admin email verification prompt and post-by-email. Every option is off by default, and critical notices such as a failed core update are always kept SCALE, PROFILES AND ANALYZER Savings indicator: HTTP requests removed, CSS/JS saved and active optimizations at a glance Quick profiles: Personal Blog, WooCommerce Store, Landing Page and Maximum Cleanup Site analyzer: personalized recommendations based on your active plugins and content, page cache included Import and export your whole configuration as a JSON file COMPATIBILITY AND EXTENSIBILITY The plugin includes filters for developers: dietpress_critical_css – Customize the inline critical CSS dietpress_critical_css_handles – Define which CSS handles are critical dietpress_skip_defer_script_handles – Opt scripts out of the JavaScript defer dietpress_skip_defer_style_handles – Opt stylesheets out of the CSS deferral dietpress_preconnect_hints – Customize preconnect origins dietpress_dns_prefetch_domains – Customize DNS prefetch domains dietpress_critical_fonts – Define critical fonts to preload dietpress_exclude_local_fonts – Exclude Google Fonts stylesheets from local hosting dietpress_selective_{module}_has_content – Mark a page as showing the content of a selective loading module, so its assets are kept. The module is wc, cf7, formidable, everest_forms or revslider dietpress_selective_{module}_styles / dietpress_selective_{module}_scripts – Adjust the handles removed by each module dietpress_selective_page_hides_content – Mark a page as rendering content the content scan cannot reach, so no module removes anything (this is what handles Elementor) dietpress_selective_is_wc_page – Override the WooCommerce page detection of selective loading dietpress_selective_wc_keep_cart_fragments – Keep the cart fragments script when your theme has a hand-coded mini-cart dietpress_selective_cf7_has_form – Mark pages that load a Contact Form 7 form dynamically dietpress_selective_blocks_dequeue – Override the block library dequeue decision dietpress_selective_everest_forms_dequeue_dashicons – Keep Dashicons when another plugin enqueues it directly dietpress_native_sitemap_in_use – Tell DietPress your plugin builds on the native WordPress sitemap, so the option that removes it becomes unavailable dietpress_cache_bypass – Keep the current page out of the page cache dietpress_cache_bypass_cookies – Adjust the cookie name prefixes that make a visitor uncacheable dietpress_cache_ignored_params – Adjust the query parameters that do not change the page dietpress_cache_exclude_urls – Adjust the excluded URL patterns dietpress_cache_post_urls – Adjust the URLs purged along with a post Compatible with: Well-coded themes and page builders (Divi, Elementor, Beaver Builder, Bricks Gutenberg) Cache plugins (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, etc.). The one exception is the optional page cache module, which will not run beside another page cache and says so; everything else in DietPress works alongside them as it always has Security plugins (DietPress focuses on performance and deliberately leaves security to them; we recommend our free Vigilant) CDNs (Cloudflare, StackPath, KeyCDN, etc.) thanks to CORS and Vary headers WordPress Multisite (except the optional page cache module, which does not support it yet) HOW TO VERIFY THE OPTIMIZATIONS Cache rules: check your .htaccess for a block marked # BEGIN DietPress with immutable Cache-Control headers Logo preload: view page source and look for pointing to your logo Critical CSS: view source and look for in the head Compression: test at giftofspeed.com/gzip-test Always measure with tools like Google PageSpeed, GTMetrix or WebPageTest, and run each test at least twice to account for caching. Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.