Mark Jaquith

<p>Encute provides a fluent, declarative API for site owners to manipulate the scripts and styles that WordPress, themes, and plugins shove onto their site. Move things into the footer, defer loading, remove assets entirely. Or load scripts async, or as modules, or as nomodule!</p>
<p>Here’s an example of how you could use the plugin:</p>
<pre><code><?php

use CWS\Encute\{ Plugin, Script, Style };

add_action(Plugin::class, function (Plugin $plugin) {
    $isContactPage = fn () => is_page('contact');
    Script::get('contact-form-7')->keepIf($isContactPage)->footer()->defer();
    Style::get('contact-form-7')->keepIf($isContactPage)->footer()->defer();

    Style::get(['mediaelement', 'wp-mediaelement'])->footer()->defer();
    Style::get('material-icons')->defer();
    Script::get('jquery')->remove();
});
</code></pre>
<h3>Wrapper</h3>
<p>Always run code in this wrapper:</p>
<pre><code>add_action(\CWS\Encute\Plugin::class, function (\CWS\Encute\Plugin $encute) {
    // Your code here.
});
</code></pre>
<p>This wrapper will be a no-op if Encute is not available, and it will both wait for Encute to be available to run, and pass you Encute’s main class instance.</p>
<h3>Fluency</h3>
<p>Both <code>Script::get()</code> and <code>Style::get()</code> return an instance of themselves, as do all calls to their methods, so you can just chain your calls.</p>
<h3>Script</h3>
<ul>
<li><code>static CWS\Encute\Script::get(string $handle): CWS\Encute\Script</code> — get a Script instance for that handle.</li>
<li><code>CWS\Encute\Script::module(): CWS\Encute\Script</code> — make the script a module.</li>
<li><code>CWS\Encute\Script::noModule(): CWS\Encute\Script</code> — make the script nomodule.</li>
<li><code>CWS\Encute\Script::footer(): CWS\Encute\Script</code> — send the script to the footer (along with its entire dependency family).</li>
<li><code>CWS\Encute\Script::async(): CWS\Encute\Script</code> — make the script async.</li>
<li><code>CWS\Encute\Script::defer(): CWS\Encute\Script</code> — make the script defer.</li>
<li><code>CWS\Encute\Script::remove(): CWS\Encute\Script</code> — remove the script.</li>
<li><code>CWS\Encute\Script::removeIf(callable $callback): CWS\Encute\Script</code> — remove the script if the callback resolves as true.</li>
<li><code>CWS\Encute\Script::keepIf(callable $callback): CWS\Encute\Script</code> — keep the script if the callback resolves as true (else remove it).</li>
</ul>
<h3>Style</h3>
<ul>
<li><code>static CWS\Encute\Style::get(string $handle): CWS\Encute\Style</code> — get a Style instance for that handle.</li>
<li><code>CWS\Encute\Style::footer(): CWS\Encute\Style</code> — send the style to the footer (along with its entire dependency family).</li>
<li><code>CWS\Encute\Style::defer(): CWS\Encute\Style</code> — defer the style’s loading.</li>
<li><code>CWS\Encute\Style::remove(): CWS\Encute\Style</code> — remove the style.</li>
<li><code>CWS\Encute\Style::removeIf(callable $callback): CWS\Encute\Style</code> — remove the style if the callback resolves as true.</li>
<li><code>CWS\Encute\Style::keepIf(callable $callback): CWS\Encute\Style</code> — keep the style if the callback resolves as true (else remove it).</li>
</ul>


Encute

Fluent API for site owners to manipulate the scripts and styles on the frontend of their site.

TechWebUX

Aleksandar Urošević

<p><strong>Head & Footer Code</strong> plugin helps you add custom code snippets (JavaScript, CSS, or HTML) to the page even if you are not a programmer. It could be within the <code><head></code> (site verification code for various services, custom styles, meta or Webfont link), right after opening <code><body></code> (pixel tracking, analytics or heatmap code) or just before closing <code></body></code> tag.</p>
<p>Go to <strong>Tools</strong> → <strong>Head & Footer Code</strong> in WordPress Dashboard. Insert custom code to HEAD, BODY or FOOTER section (depending on what you have to do).</p>
<p>All magic is done by hooking to WordPress hooks <code>wp_head</code>, <code>wp_footer</code> and <code>wp_body_open</code>.</p>
<blockquote>
<p>💡 Trial Head & Footer Code plugin on a free dummy website before you add it on your project: <a href="https://tastewp.com/new/?pre-installed-plugin-slug=head-footer-code" rel="nofollow ugc">Test It Now!</a></p>
</blockquote>
<p>Various code snippets are supported, including but not limited to:</p>
<ul>
<li>Google Analytics 4</li>
<li>Google Tag Manager</li>
<li>Google Ads Conversion</li>
<li>Lite Analytics</li>
<li>Facebook/Meta Pixel</li>
<li>Hotjar</li>
<li>FullStory</li>
<li>Google site verification</li>
<li>Bing site verification</li>
<li>Yandex site verification</li>
<li>Alexa site verification</li>
</ul>
<h3>Homepage in Blog Posts mode</h3>
<p>If your WordPress shows the latest blog posts on the homepage, you can also add specific code only for the homepage on <strong>Tools</strong> → <strong>Head & Footer Code</strong> (there will be section <strong>Head, body and footer code on Homepage in Blog Posts mode</strong>)</p>
<h3>Article specific code</h3>
<p>To insert custom code specific for individual article (post, page or custom post type), use article-specific Metabox while editing post/page/custom post type (check out <a href="https://wordpress.org/plugins/head-footer-code/#screenshots" rel="ugc">Screenshots</a>). There choose if that specific code appends to site-wide code defined on <strong>Tools</strong> → <strong>Head & Footer Code</strong>, or to replace it.</p>
<h3>Category specific code</h3>
<p>You can also define a Category specific code on each individual category.</p>
<p>Other taxonomies (tag and custom taxonomy) do not have available their specific code, but for them a Global code is used instead.</p>
<h3>Video guide</h3>
<p><iframe loading="lazy" title="Head Footer Code: How To Install, Configure and Use" width="750" height="563" src="https://www.youtube.com/embed/Gd41Dv09UC4?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></p>
<h3>Do you need our support?</h3>
<p>If <strong>Head & Footer Code</strong> does not work on your project, please let us know by <a href="https://wordpress.org/support/plugin/head-footer-code/#new-topic-0" rel="ugc">raising a new support ticket</a> in the <a href="https://wordpress.org/support/plugin/head-footer-code/" rel="ugc">Community Forum</a> and describe what does not works and how to reproduce the issue. We will make sure to resolve the issue as soon as possible.</p>
<p>If you find <strong>Head & Footer Code</strong> useful for your project, please <a href="https://wordpress.org/support/plugin/head-footer-code/reviews/#new-post" rel="ugc">review plugin</a>.</p>
<h3>Features</h3>
<ul>
<li><strong>Multisite</strong> and <strong>PHP 8.3</strong> compatible!</li>
<li>Set site-wide custom content for:
<ul>
<li>head page section (before the <code></head></code>)</li>
<li>body section (after the <code><body></code>) – <strong>Requires WordPress 5.2!</strong></li>
<li>footer page section (before the <code></body></code>)</li>
</ul>
</li>
<li>Homepage in Blog Posts mode:
<ul>
<li>set homepage specific custom code for head, body and/or footer</li>
<li>toggle homepage specific custom code on paged Homepage (page 2, 3, a nd so on)</li>
</ul>
</li>
<li>Set article specific custom code for:
<ul>
<li>head page section (before the <code></head></code>)</li>
<li>body section (after the <code><body></code>) – <strong>Requires WordPress 5.2!</strong></li>
<li>footer page section (before the <code></body></code>)</li>
</ul>
</li>
<li>Set category specific custom code for head, body and/or footer of the page</li>
<li>Choose priority of printed custom code to head/body/footer sections (lower number mean far from <code></head></code> and <code></body></code> and closer to <code><body></code>, higher number means closer to <code></head></code> and <code></body></code> and farther to <code><body></code>)</li>
<li>Choose which post types will have enabled article specific head/body/footer fields</li>
<li>Choose should article specific head/body/footer code be appended to site-wide code, or will replace site-wide code</li>
<li>View on Posts/Pages/Custom Post Types listing if article has defined any article specific custom code</li>
<li>Site-wide section is located under <strong>Tools</strong> > <strong>Head & Footer Code</strong></li>
<li>If you have set WP_DEBUG constant in <code>wp-config.php</code> to <code>true</code>, you’ll see site-wide and article specific entries in page source code wrapped to comments.</li>
<li>[NEW] allow unprivileged user roles Editor and Author to manage article-specific code on single site and multisite (disabled by default)</li>
</ul>
<h3>Data stored in database</h3>
<p>General settings (HEAD, BODY, FOOTER global code and priority, Homepage code and behaviour) saves in WordPress option <code>auhfc_settings</code>.<br />
Each post/page/custom post type specific HEAD, BODY and FOOTER code and behaviour saves to post meta <code>_auhfc</code>.<br />
Each category specific HEAD, BODY and FOOTER code and behaviour saves to taxonomy meta <code>_auhfc</code>.</p>
<p>During the Uninstall process all these data has been deleted from the database.<br />
In case you wish to reinstall plugin, <strong>DO NOT UNINSTALL IT</strong> although <strong>Deactivate</strong>, then delete the directory <code>/wp-content/plugins-head-footer-code</code> and then reinstall plugin.</p>
<h3>Permissions on Multisite WordPress</h3>
<ol>
<li>Access to <strong>Global</strong>: only Super Admin and Administrator</li>
<li>Access to <strong>Article specific</strong>: Super Admin, Administrator; <strong>optional</strong>: Editor and Author</li>
<li>Access to <strong>Category specific</strong>: only Super Admin and Administrator</li>
</ol>


Head & Footer Code

This plugin is what exactly I'm looking for to add custom javascript and CSS codes to specific pages without inserting them inside the template.

A must have plugin

Easy add site-wide, category and article specific custom code before the closing </head> and </body>, or after opening <body> tag.

Encute vs Head & Footer Code