Scott Reilly

<p>Ever want to tweak the appearance of the WordPress admin pages by hiding stuff, moving stuff around, changing fonts, colors, sizes, etc? Any modification you may want to do with CSS can easily be done via this plugin.</p>
<p>Using this plugin you’ll easily be able to define additional CSS (inline and/or files by URL) to be added to all administration pages. Hooks are provided to customize the output of the CSS, the CSS files, and if/when the CSS should even be output (see Hooks section).</p>
<p>Links: <a href="https://coffee2code.com/wp-plugins/add-admin-css/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/add-admin-css/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/add-admin-css/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a></p>
<h3>Developer Documentation</h3>
<p>Developer documentation can be found in <a href="https://github.com/coffee2code/add-admin-css/blob/master/DEVELOPER-DOCS.md" rel="nofollow ugc">DEVELOPER-DOCS.md</a>. That documentation covers the hooks provided by the plugin.</p>
<p>As an overview, these are the hooks provided by the plugin:</p>
<ul>
<li><code>c2c_add_admin_css</code>             : Filter to customize the CSS that should be added directly to the admin page head.</li>
<li><code>c2c_add_admin_css_files</code>       : Filter to customize the list of CSS files to enqueue in the admin.</li>
<li><code>c2c_add_admin_css_disable_css</code> : Filter to customize if the CSS defined via this plugin should be output or not.</li>
</ul>


Add Admin CSS

This plugin did *exactly* what I wanted. A plugin had dropped some ad stuff into the Publish box, but it had a good CSS class, so I just hid it.

I really like that the text field for holding the CSS is intelligent and does things like auto include closing brackets, code coloring, etc.

Worked perfectly

Easily define additional CSS (inline and/or by URL) to be added to all administration pages.

Utsav Ladani

<p>MachStyle helps your pages feel faster by loading critical styles first and delaying selected non-critical CSS.</p>
<p>You decide where this happens using simple rules. For many sites, this can help improve Core Web Vitals.</p>
<p>MachStyle is designed for practical, low-risk testing:</p>
<ul>
<li>Create rules for specific page groups, post types, or URL patterns.</li>
<li>Test changes safely in Test Flight before they affect real visitors.</li>
<li>Compare results in performance tools like PageSpeed Insights before going live.</li>
<li>Copy tested rules to live settings when ready.</li>
</ul>
<p>Small, measured changes work best. Test, compare, then roll out.</p>
<h3>How to Use</h3>
<ol>
<li>Open MachStyle and go to <code>Test Flight</code>.</li>
<li>Add one rule for one page group, such as the home page, a post type, or a URL pattern.</li>
<li>Add the style handles you want to defer. Use the Audit Panel to find style handles.</li>
<li>Check the page on desktop and mobile.</li>
<li>Run PageSpeed on the Test Flight URL and compare the result with your normal live URL.</li>
<li>If the page looks correct and the metrics improve, copy the rules to <code>Live Settings</code>.</li>
<li>Enable live optimization.</li>
</ol>
<h3>How to Use Audit Panel</h3>
<p>Audit Panel is a tool that helps you find style handles to defer.</p>
<ol>
<li>Open the frontend of your website and open Audit Panel from MachStyle menu in admin bar.</li>
<li>Click on any stylesheet to temporarily remove its styling. This shows you what the page looks like for a fraction of second during load.</li>
<li>Look at the top of your site. If it still looks readable and organized without that style, it’s a great candidate to stay deferred.</li>
<li>If the page looks messy or the header breaks, that style is important for the first impression. Click it again to turn it back on.</li>
<li>Once finished, click <strong>Copy Handles</strong> button to get your optimized list and add it to your MachStyle settings.</li>
</ol>
<h3>What to Defer First</h3>
<p>Start with styles that are useful but not needed immediately:</p>
<ul>
<li>Footer styles</li>
<li>Slider and carousel styles</li>
<li>Form styles on pages that do not show forms right away</li>
<li>Social share or widget styles below the fold</li>
<li>Extra builder or block styles not needed at first paint</li>
</ul>
<h3>What Not to Defer</h3>
<p>Avoid deferring styles that control first-view layout:</p>
<ul>
<li>Main theme layout styles</li>
<li>Header, menu, and hero section styles</li>
<li>Checkout and cart critical styles</li>
<li>Any style that causes visible layout shifts when delayed</li>
</ul>
<h3>Development & Contribution</h3>
<p>MachStyle is open source and welcomes contributions!</p>
<ul>
<li><strong>GitHub Repository</strong>: https://github.com/Utsav-Ladani/MachStyle</li>
<li><strong>Report Issues</strong>: https://github.com/Utsav-Ladani/MachStyle/issues</li>
<li><strong>Feature Requests</strong>: https://github.com/Utsav-Ladani/MachStyle/issues</li>
<li><strong>Contribute Code</strong>: Fork the repository and submit pull requests</li>
</ul>


MachStyle

MachStyle helps your pages feel faster by loading critical styles first and delaying selected non-critical CSS.

Add Admin CSS vs MachStyle