abdelhalimkhouas

<p><strong>Scripts and Styles Manager</strong> helps you optimize your WordPress website’s performance by letting you manage the scripts and styles loaded on each page. Identify and disable assets that you don’t need on specific pages, reducing page load times and enhancing user experience.</p>
<p><strong>Features:</strong><br />
– View all scripts and styles loaded on a specific page.<br />
– Toggle the loading of assets on/off with a simple interface.<br />
– Copy the source URL of an asset to the clipboard.<br />
– Pagination and search for easy navigation of assets.<br />
– Responsive and user-friendly design.<br />
– Lightweight and optimized for performance.</p>
<p>This plugin is ideal for users who want to optimize their website’s loading speed without diving into code.</p>
<h3>License</h3>
<p>This plugin is licensed under the MIT License. See <a href="https://opensource.org/licenses/MIT" rel="nofollow ugc">License URI</a> for details.</p>


Scripts and Styles Manager

Easily manage the scripts and styles loaded on your WordPress pages to improve performance by toggling off unnecessary assets.

Dominik Schilling

benlumley

<p>Filename based cache busting for WordPress scripts/styles using last modified date.</p>
<p>Stop telling clients or users to hard refresh / shift refresh. The url to all of the css/js files on your site will change automatically whenever the files are modified. You can set proper long cache lifetimes to help get top scores on Google Pagespeed without running into cached css/javascript problems.</p>
<p>Based on this gist https://gist.github.com/ocean90/1966227 from Dominik Schilling, I’ve enhanced it by automatically replacing the asset version with the files modification time and automatically editing htaccess – making it install + forget.</p>
<p>Includes querystring option as a fallback – which works in more scenarios.</p>
<h3>Webservers</h3>
<h4>Apache</h4>
<p>The plugin should add what it needs to your .htaccess file jsut like WP itself. But if for any reason that doesn’t work for you – here’s what it adds:</p>
<pre><code># FBACB
<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /

  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule ^(.+)\.([0-9\.]+)\.(js|css)$ $1.$3 [L]
</IfModule>

# still fbacb
<IfModule mod_expires.c>
    ExpiresActive on
    ExpiresByType text/css                            "access plus 1 year"
    ExpiresByType application/javascript              "access plus 1 year"
</IfModule>
# END FBACB
</code></pre>
<h4>NGINX</h4>
<pre><code> location ~* ^(.+)\.(?:\d+)\.(min.js|min.css|js|css)($|\?.*$) {
   try_files $uri $1.$2;
 }
</code></pre>
<h3>Host specific notes</h3>
<p>Some webhosts need a bit of custom config to get the filename based urls working.</p>
<h4>WP Engine</h4>
<p>To work on WP-Engine, you’ll need the following redirect added via my.wpengine -> installname -> Redirect rules</p>
<pre><code> Source: ^(.+)\.([0-9\.]+)\.(js|css)$
 Dest: $1.$3
 Type: break (this is under advanced)
</code></pre>
<h4>CloudWays</h4>
<p>Just works.</p>
<h4>Flywheel</h4>
<p>Just works.</p>
<h4>PHP Fallback</h4>
<p>If your webserver is failing to serve assets using url rewriting, the plugin attempts to serve them itsef (ie: via PHP). Obviously this is slow/less than ideal in production (it’ll be much slower) – so you should configure your web server correctly to serve the files. If you see this HTTP header “FBACB-Php-Fallback: yes” on your assets, this applies to you.</p>
<p>Note that hosts are increasingly configured to serve css/js directly from disk and won’t fall back to PHP + WordPress error handling – this fallback then won’t work.</p>


Filename based asset cache busting

Filename based cache busting for WordPress scripts/styles using last modified date.

Scripts and Styles Manager vs Filename based asset cache busting