Firas Abd Alrahman

<p>Once you install WordPress with some plugins and finish customizing your theme, you usually stock with performance issues.<br />
Installing and configuring a good caching plugin, you will enhance your first byte and website speed, but you getting low rank on google page speed.<br />
The reason for that, each WordPress plugin come with it\’s assets (js/scss files) and most of them are not really used or required, but WordPress does not offer a way to control those injected files in your themes.<br />
GSP Assets Manager offer an easy way to list, review and control WordPress assets.<br />
You can disable, move to the header, move to the footer, toggle async for javascript and WordPress without writing a single code.<br />
The plugin also offer a live preview for CSS, so you can disable the CSS file and see the result directly on your website before you save, to avoid breaking the website style.</p>


GSP Assets Manager (Easy Live Assets Editor)

GSP Assets Manager will allow you to live review and control WordPress javascript files and stylesheets. Optimize google page speed rank within 5 minu …

Steve Grunwell

Growella

<p>WordPress asset versioning can be a double-edged sword: on one-hand, it’s extremely effective for cache-busting, ensuring you aren’t sharing stale scripts or styles to your visitors. On the other hand, having to manually increment a version number is a pain (even <a href="https://10up.github.io/Engineering-Best-Practices/php/#asset-versioning" rel="nofollow ugc">as a constant</a>), often resulting in a version control history full of “bumping the version number” commits.</p>
<p>Dynamic Asset Versioning aims to simplify this process: if an enqueued asset doesn’t have an explicit version number, the plugin will get the timestamp of the last time the file was changed and use that as the version number. It’s easy: you touch the file, the version number is updated automatically.</p>
<h4>Usage</h4>
<p>Once Dynamic Asset Versioning is active, it will automatically determine version numbers based on file modification time for any [non-core] files that have been enqueued using <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_style/" rel="nofollow ugc"><code>wp_enqueue_style()</code></a> or <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_style/" rel="nofollow ugc"><code>wp_enqueue_script()</code></a>.</p>
<p><strong>Example</strong></p>
<pre><code>wp_enqueue_style(
    'my-theme-styles',
    get_template_directory_uri() . '/assets/css/my-styles.css',
    array( 'some-other-styles' ),
    false, // Don't worry about it, Dynamic Asset Versioning has you covered!
    'screen'
);
</code></pre>
<h4>Special thanks</h4>
<p>A special thanks goes out to <a href="http://10up.com" rel="nofollow ugc">10up</a>, who helped inspire the original concept of this plugin.</p>


Dynamic Asset Versioning

Exactly what I was looking for. Great stuff. Thanks guys

Amazing

Dynamically set asset version numbers based on file modification times, preventing stale caches.

GSP Assets Manager (Easy Live Assets Editor) vs Dynamic Asset Versioning