John Dalesandro

<p><strong>Head Trimmer</strong> gives you granular control over what WordPress automatically outputs in the HEAD element of every page. Each option is independent; enable only the removals that make sense for your site.</p>
<p>Removing unnecessary HEAD elements reduces page weight, eliminates potential security signatures such as the WordPress version number, and keeps your generated source code clean.</p>
<p>All settings are opt-in. Nothing is removed until you enable it on the Admin <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Head Trimmer screen.</p>
<p>Removal options include:</p>
<ul>
<li>WordPress Version (generator meta tag)</li>
<li>WordPress Version from Script and Style URLs</li>
<li>All Other Version Signatures from Script and Style URLs</li>
<li>Shortlink</li>
<li>Shortlink from HTTP Response Headers</li>
<li>Canonical</li>
<li>Relational Links for Posts Adjacent to Current Post</li>
<li>RSS Feeds (removes head links and disables feed endpoints)</li>
<li>Really Simple Discovery Link for xmlrpc (rsd_link)</li>
<li>Windows Live Writer Manifest File Link (wlwmanifest_link)</li>
<li>oEmbed Discovery Links</li>
<li>REST API Link and REST API Link Header</li>
<li>Emoji Support</li>
<li>Global Styles and SVG Filters (duotone filters)</li>
<li>Gutenberg Block CSS Styles (or optionally set ‘should_load_separate_core_block_assets’ to load block styles only when needed)</li>
<li>Classic Theme CSS Styles (classic-theme-styles)</li>
<li>DNS Prefetch for //s.w.org</li>
<li>DNS Prefetch for Google Fonts //fonts.googleapis.com</li>
<li>jQuery</li>
<li>JavaScript Import Map (added in WordPress 6.5)</li>
<li>Interactivity API (added in WordPress 6.5)</li>
<li>Image Auto Sizes Styles (added in WordPress 6.7)</li>
<li>Speculation Rules (added in WordPress 6.8)</li>
<li>Comment Reply Script (loads only on singular posts and pages where comments are open)</li>
</ul>


Head Trimmer

Selectively remove WordPress version information, feeds, shortlinks, emoji support, scripts, styles, and other automatically generated extras from the …

Joshua David Nelson

<p>This small plugin moves scripts to the footer. Note that this only works if you have plugins and a theme that utilizes <code>wp_enqueue_scripts</code> correctly.</p>
<p>You can disable the plugin on specific pages and posts directly via the post/page edit screen metabox.</p>
<p>You can disable the plugin on specific archive pages (blog page, search page, post type and taxonomy archives) via the settings page.</p>
<p><strong>Everything Broken?</strong> Try placing jQuery back into the header via Settings > Scripts to Footer, “Keep jQuery in the Header” checkbox. If that doesn’t work, refer to the walkthrough below for using the <code>stf_exclude_scripts</code> filter for the script that is causing the issue.</p>
<p>Check out the <a href="https://github.com/joshuadavidnelson/scripts-to-footer/wiki" rel="nofollow ugc">documentation</a> on <a href="https://github.com/joshuadavidnelson/scripts-to-footer" rel="nofollow ugc">GitHub</a> or some quick walkthroughs below.</p>
<h4>Keeping specific Scripts in the Header</h4>
<p>As of version 0.6 you can now keep specific scripts in the header. Note: this will print any scripts they depend on as well (if you want to keep <code>jquery-effects-core</code> in the header, you’ll also get <code>jQuery</code> in the header, so no need to add both).</p>
<p>Specifically for jQuery, see the settings page option, as it is a common request we’ve built it into the settings.</p>
<p>For any other scripts, use this filter:</p>
<pre><code>add_filter( 'stf_exclude_scripts', 'jdn_header_scripts', 10, 1 );
function jdn_header_scripts( $scripts ) {

    $scripts[] = 'backbone'; // Replace 'backbone' with the script slug

    return $scripts;
}
</code></pre>
<p>You will need the correct script slug, which is used when the script is registered, and the script will only be printed into the header <em>if it’s enqueued</em>. Check out the scripts that come registered <a href="https://codex.wordpress.org/Function_Reference/wp_enqueue_script#Default_Scripts_Included_and_Registered_by_WordPress" rel="nofollow ugc">out-of-the-box with WordPress</a>.</p>
<p><strong>Note:</strong> As of version 0.6.3, <a href="https://codex.wordpress.org/Conditional_Tags" rel="nofollow ugc">conditional tags</a> will work with the <code>stf_exclude_scripts</code> filter.</p>
<h4>Custom Post Type Support</h4>
<p>If you’re comfortable with code you can use the <code>scripts_to_footer_post_types</code> filter to change the post types this applies to (it only applies to pages and posts by default). For example, if you have a custom post type called “project” you could add support for this metabox via the post type filter like this:</p>
<pre><code>function stf_add_cpt_support( $post_types ) {

    $post_types[] = 'project';

    return $post_types;
}
add_filter( 'scripts_to_footer_post_types', 'stf_add_cpt_support' );
</code></pre>
<h4>Excluding Pages/Posts/Templates Via Filter</h4>
<p>You can either use the checkbox option to disable the plugin’s action on a specific page/post, or you can utilize a filter. The filter also passes the post/page id, if there is one (archive templates don’t have ids!).</p>
<p>For example, for the “page” post type:</p>
<pre><code>function stf_exclude_my_page( $exclude_page, $post_id ) {

    if ( is_front_page() ) {
        $exclude_page = 'on'; // this turns on the "exclude" option
    }

    return $exclude_page;
}
add_filter( 'stf_page', 'stf_exclude_my_page' );
</code></pre>
<p>Replace <code>stf_page</code> with <code>stf_post</code> for posts, or the slug of your custom post type. For instance, a post type called “project” can be filtered with <code>stf_project</code>.</p>
<h4>More Documentation</h4>
<p><a href="https://github.com/joshuadavidnelson/scripts-to-footer/wiki" rel="nofollow ugc">See the plugin’s wiki</a>.</p>
<h4>Development / Contributing</h4>
<p><a href="https://github.com/joshuadavidnelson/scripts-to-footer" rel="nofollow ugc">View this plugin on GitHub</a>.</p>
<h4>Support</h4>
<p>Please feel free to open a <a href="https://github.com/joshuadavidnelson/scripts-to-footer/issues" rel="nofollow ugc">Github Issue</a> to report conflicts or goto <a href="https://wordpress.org/support/plugin/scripts-to-footerphp" rel="ugc">the WP.org support forum</a>. If there is something wrong with Scripts-to-Footer, we’ll update it. However, if it’s a another plugin or theme we can only contact the developer with the issue to attempt to resolve it.</p>


Scripts To Footer

Your plugin deserves lots of love and support, added to favourite. I will make sure to recommend it as much as possible. Thank you so much dear Developer.

Reliable, I can trust, happily using since 2 months

Move your scripts to the footer to help speed up perceived page load times and improve user experience.

Head Trimmer vs Scripts To Footer