minhbeplus

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:
<ul>
<li>JavaScript delay and defer with per-script exclude list</li>
<li>CSS file and inline minification with cache</li>
<li>Non-render-blocking stylesheet loading</li>
<li>Lazy load images with IntersectionObserver fallback</li>
<li>Remove emoji, wp-embed, Gutenberg CSS, WooCommerce assets on non-shop pages</li>
<li>HTML minification and comment stripping</li>
<li>Browser cache and gzip/brotli rules via .htaccess</li>
<li>Per-page option to disable the cache for specific posts/pages</li>
</ul>
<h3>Settings Reference</h3>
Navigate to Settings > Beplus Performance Booster to configure the plugin.
<h4>⚡ JavaScript Optimization</h4>
Delay JS Execution 
Default: off
Delays all non-excluded front-end scripts until the first user interaction (click, 
scroll, keydown, or touchstart). After 5 seconds without interaction the scripts 
load automatically as a safety fallback. Best for scripts that are not needed until 
the user actually engages with the page (e.g. chat widgets, marketing pixels).
Defer Non-Critical JS 
Default: off
Adds the <code>defer</code> attribute to every non-excluded <code><script></code> 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 <code>src</code> 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: <code>jquery</code>, <code>woocommerce</code>, <code>my-critical-script</code>
<h4>🎨 CSS Optimization</h4>
Minify Inline CSS 
Default: off
Strips block comments (<code>/* … */</code>), collapses redundant whitespace, and removes 
trailing semicolons from every inline <code><style></code> block in <code><head></code>. License 
comments (<code>/*! … */</code>) are preserved. Spaces around <code>+</code> are intentionally kept 
so <code>calc(100% + 20px)</code> 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 <code>*.min.css</code> 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 <code><link rel="stylesheet"></code> tags to the preload + onload swap pattern:
<pre><code><link rel="preload" as="style" onload="this.onload=null;this.rel='stylesheet'">
<noscript><link rel="stylesheet" ...></noscript>
</code></pre>
This prevents stylesheets from blocking the initial render. A <code><noscript></code> 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 <code>href</code> contains a listed keyword are 
left completely untouched by both the Non-Blocking and Minify CSS Files features.
<h4>🖼️ Lazy Load Images</h4>
Enable Lazy Loading 
Default: off
Adds <code>loading="lazy"</code> to qualifying <code><img></code> tags found in post content, featured 
images, widget text, and <code><picture></code> elements. For browsers that do not support the 
native <code>loading</code> 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 <code>loading="eager"</code> instead of <code>loading="lazy"</code>. 
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 <code><img></code> that has one of these classes loads 
eagerly (not lazily).
Example: <code>hero-image, no-lazy, skip-lazy</code>
Exclude by Element ID 
Default: empty
Comma-separated element IDs. Any <code><img></code> with a matching <code>id</code> attribute loads 
eagerly.
Example: <code>hero-banner, site-logo</code>
Exclude by Filename 
Default: empty
Comma-separated partial filename strings. Any <code><img></code> whose <code>src</code> URL contains one 
of these strings loads eagerly.
Example: <code>logo, hero, banner</code>
<h4>🗑️ Remove Unused Assets</h4>
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 <code>wp-embed.js</code> script and the oEmbed discovery links added to <code><head></code>. 
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 <code>wp-block-library</code>, <code>wp-block-library-theme</code>, and <code>global-styles</code> 
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.
<h4>📄 HTML Optimization</h4>
Minify HTML Output 
Default: off
Collapses redundant whitespace between HTML tags in the full page output. Content 
inside <code><pre></code>, <code><textarea></code>, <code><script></code>, and <code><style></code> 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 <code>//</code> single-line and <code>/* … */</code> block comments from inline <code><script></code> 
blocks in the HTML output. String literals and template literals are never 
modified. License comments (<code>/*! … */</code>) are preserved.
Remove Inline CSS Comments 
Default: off
Removes <code>/* … */</code> block comments from inline <code><style></code> blocks in the HTML output.
<h4>🚀 Browser Cache Headers (.htaccess)</h4>
Enable Browser Caching 
Default: off 
Requires: Apache with mod_expires, mod_headers, mod_deflate. .htaccess writable.
Injects the following directives into the root <code>.htaccess</code> file inside a clearly 
labelled block that is never duplicated:
<ul>
<li>Gzip compression (mod_deflate) for HTML, CSS, JS, JSON, SVG, and fonts.</li>
<li>Brotli compression (mod_brotli, Apache 2.4.26+) for the same types.</li>
<li>Expires headers (mod_expires): 1-year cache for static assets; no-cache 
for HTML and API responses.</li>
<li>Cache-Control headers (mod_headers): <code>max-age=31536000, public, immutable</code> 
for CSS, JS, images, and fonts.</li>
</ul>
Disabling this option or deactivating the plugin removes the injected block cleanly.
<h4>📦 JS File Minification & Cache</h4>
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 (<code>https://</code>). Already-minified <code>*.min.js</code> 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 
(<code>wp-content/uploads/bepluspb-cache/</code>). 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.
<h4>Per-Page Cache Disable (Meta Box)</h4>
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.

Beplus Performance Booster

Lightweight WordPress optimizer with JS/CSS minification, lazy loading, asset cleanup, and browser cache headers. Zero dependencies.

Blogestudio

Pau Iglesias

Improve user experience by having your above-the-fold (top of the page) CSS styles in-page.
Even if the rest of the CSS files take a seconds to load, these specific CSS styles displayed from the head section ensure a quick rendering of your page and better score in testing systems like Google Page Speed Insights.
But you do not need to maintain two separate stylesheets, just select specific fragments of your theme style file with a special markup to create an above-the-fold styles joining the CSS fragments in the head section.
This plugin enables a special open and close tags that you can insert editing your style.css theme file to surround pieces of code:
[css-above-the-fold]
… Your theme CSS code fragment …
[/css-above-the-fold]
But this syntax is not an standard CSS, so you need to include this tags between CSS comments, there are two ways to do it:
<h3>1. Comment whole section</h3>
The easiest way, the CSS is rendered only in the head but not in the stylesheet. 
This kind of markup does not allow to use your own CSS comments inside the fragment. 
Take care to use this way only when the plugin is active, because you are commenting some parts of your theme stylesheet.
/* [css-above-the-fold]
… CSS code fragment …
[/css-above-the-fold] */
<h3>2. Comment only the tags</h3>
The unobtrusive way, it allows you to include comments inside fragments, but the fragments are rendered both in the head section and the CSS file. 
This way is plugin-independent, and your theme stylesheet will keep running with this plugin activated or not.
/* [css-above-the-fold] */
… CSS code fragment …
/* [/css-above-the-fold] */
You can use these two kinds of markup combined in your CSS File.
The resulting CSS fragments introduced in the header are compacted and minified.
This plugin only read the style.css file when it is modified, and stores the results using the WP options API.

CSS Above The Fold

Good idea for a plugin. Works perfectly. Thanks.



Good idea

Faster CSS browser rendering displaying selected fragments of your theme stylesheet file directly into the head section.

Beplus Performance Booster vs CSS Above The Fold