{"id":4826,"date":"2025-08-14T13:26:20","date_gmt":"2025-08-14T11:26:20","guid":{"rendered":"https:\/\/wpmastertoolkit.com\/module\/head-sorter\/"},"modified":"2025-08-14T14:16:46","modified_gmt":"2025-08-14T12:16:46","slug":"head-sorter","status":"publish","type":"module","link":"https:\/\/wpmastertoolkit.com\/en\/module\/head-sorter\/","title":{"rendered":"Head Sorter"},"content":{"rendered":"

Head Sorter - Intelligent reorganization of the <head><\/code> to boost speed and SEO<\/h1>\n\n\n\n

For many WordPress sites, the order of tags in the <head><\/code> is silent chaos: metadata drowns out, CSS arrives too late, scripts block... The result: slower rendering, lower Web Vitals metrics and poorer SEO. The module Head Sorter<\/strong> from WPMasterToolKit<\/strong> has been created to put things in order automatically - without complicated settings - and put what really matters first.<\/p>\n\n\n\n

Which plug-in can the \"Head Sorter\" module replace?<\/h2>\n\n\n\n

In many cases, Head Sorter can replace small plugins dedicated to \"head tag sorting\", load order optimizations, or in-house snippets that attempt to manually move <meta><\/code>, <link><\/code> and <script><\/code>. Here, everything is managed systematically and securely via an HTML parser.<\/p>\n\n\n\n

How it works (in plain English)<\/h2>\n\n\n\n
    \n
  1. Intercepting front-end rendering<\/strong>
    The module attaches to template_redirect<\/code> (priority -1000<\/strong>) to start a output buffer<\/strong> (output buffering). It does not that the Front-end<\/strong>.<\/li>\n\n\n\n
  2. HTML detection<\/strong>
    If the page does not contain <\/html><\/code>the content remains unchanged.<\/li>\n\n\n\n
  3. Analysis of <head><\/code> with DOMDocument<\/strong>
    The contents of the <head><\/code> is loaded into a DOMDocument<\/strong> (with silent error handling), then all child tags are evaluated and sorted<\/strong> according to a weight<\/strong>.<\/li>\n\n\n\n
  4. Sort by importance<\/strong>
    Nodes (tags, text, comments) are assigned a weight. We re-inserts<\/strong> then the elements in the <head><\/code> from most to least important, in preserving<\/strong> comments and texts.<\/li>\n<\/ol>\n\n\n\n

    The priority grid (from most to least important)<\/h3>\n\n\n\n
      \n
    • META<\/strong> (10) : charset<\/code>, viewport<\/code>and some http-equiv<\/code> reviews (content-security-policy<\/code>, content-type<\/code>, default-style<\/code>etc.)<\/li>\n\n\n\n
    • TITLE<\/strong> (9)<\/li>\n\n\n\n
    • PRECONNECT<\/strong> (8) : <link rel=\"preconnect\"><\/code><\/li>\n\n\n\n
    • ASYNC_SCRIPT<\/strong> (7) : <script src ... async><\/code><\/li>\n\n\n\n
    • IMPORT_STYLES<\/strong> (6) : <style><\/code> containing @import<\/code><\/li>\n\n\n\n
    • SYNC_SCRIPT<\/strong> (5) : <script><\/code> inline blocking (non defer<\/code>no async<\/code>no type=\"module\"<\/code>and no type<\/code> JSON)<\/li>\n\n\n\n
    • SYNC_STYLES<\/strong> (4) : <link rel=\"stylesheet\"><\/code> and <style><\/code><\/li>\n\n\n\n
    • PRELOAD<\/strong> (3) : <link rel=\"preload|modulepreload\"><\/code><\/li>\n\n\n\n
    • DEFER_SCRIPT<\/strong> (2) : <script src ... defer><\/code> or <script type=\"module\"><\/code> (without async<\/code>)<\/li>\n\n\n\n
    • PREFETCH_PRERENDER<\/strong> (1) : <link rel=\"prefetch|dns-prefetch|prerender\"><\/code><\/li>\n\n\n\n
    • OTHER<\/strong> (0): everything else, including JSON scripts (application\/ld+json<\/code>etc.) and non-element nodes (texts, comments), which are kept<\/li>\n<\/ul>\n\n\n\n

      \ud83d\udc49 In concrete terms, your critical tags (charset<\/code>, viewport<\/code>, title<\/code>) go to the top<\/strong>resources, followed by connection and CSS<\/strong> necessary for rendering, and blocking scripts are eliminated as far as possible by giving priority to async<\/code>\/defer<\/code>\/module<\/code>.<\/p>\n\n\n\n

      Why it's good for performance and SEO<\/h2>\n\n\n\n
        \n
      • Faster FCP\/LCP<\/strong> essential meta and styles arrive early, reducing initial rendering time.<\/li>\n\n\n\n
      • Less blocking JS<\/strong> scripts async\/defer\/module<\/code> are favored, reducing the impact on the critical rendering path.<\/li>\n\n\n\n
      • Technical SEO<\/strong> one <head><\/code> better structured helps engines to understand and index correctly (consistent title\/meta first).<\/li>\n<\/ul>\n\n\n\n

        Behaviors and compatibility to know<\/h2>\n\n\n\n
          \n
        • Front-end only<\/strong> : hooked on template_redirect<\/code>. The admin is not impacted.<\/li>\n\n\n\n
        • Content preservation<\/strong> comments and texts in the <head><\/code> are retained.<\/li>\n\n\n\n
        • JSON scripts<\/strong> (e.g. application\/ld+json<\/code>) : not treated as blocking scripts<\/strong> (\"OTHER\" weight) to avoid moving them aggressively.<\/li>\n\n\n\n
        • ES modules<\/strong> (type=\"module\"<\/code>): treated as defer<\/strong> by default (good for rendering).<\/li>\n\n\n\n
        • Ill-formed HTML<\/strong> DOMDocument can attempt to \"correct\" a badly structured head, but keep HTML clean for best results.<\/li>\n<\/ul>\n\n\n\n

          How to use this module<\/h2>\n\n\n\n
            \n
          1. Activate the Head Sorter module<\/strong> in WPMasterToolKit.<\/li>\n\n\n\n
          2. Empty cache<\/strong> your plugins\/server\/CDN if you use them.<\/li>\n\n\n\n
          3. Control a page<\/strong> (home page, sample article) to check the order of the <head><\/code> with the browser's dev tools.<\/li>\n\n\n\n
          4. No adjustments to make: everything is automatic<\/strong>.<\/li>\n<\/ol>\n\n\n\n

            Our technical choices (and why)<\/h2>\n\n\n\n
              \n
            • Output buffering<\/strong> at the earliest (template_redirect<\/code>priority -1000) to capture the final rendering of the page without touching the heart of WordPress or the themes.<\/li>\n\n\n\n
            • DOMDocument<\/strong> for a reliable handling<\/strong> rather than fragile regexes.<\/li>\n\n\n\n
            • Weight matrix<\/strong> clear and extensible code to prioritize :\n
                \n
              • Meta\/title<\/strong> first and foremost (web standards + SEO).<\/li>\n\n\n\n
              • Preconnect\/Preload\/Style sheets<\/strong> before blocking scripts.<\/li>\n\n\n\n
              • async<\/code>\/defer<\/code>\/module<\/code><\/strong> better off than conventional synchronous scripts.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
              • Conservatism on JSON<\/strong> : exclusion of type<\/code> containing json<\/code> from the \"synchronous script\" category to avoid affecting the markup of structured data.<\/li>\n<\/ul>\n\n\n\n

                Hooks and filters<\/h2>\n\n\n\n

                This module exposes no apply_filters<\/code> or do_action<\/code> personalized<\/strong>. Behavior is entirely internal.<\/p>\n\n\n\n

                Practical tips<\/h2>\n\n\n\n
                  \n
                • Avoid @import<\/code> in your <style><\/code> : even if they have priority here, they remain slower<\/strong> that a <link rel=\"stylesheet\"><\/code>.<\/li>\n\n\n\n
                • If a critical script needs to run early, prefer defer<\/code><\/strong> (or type=\"module\"<\/code><\/strong>) rather than synchronous, so as not to block rendering.<\/li>\n\n\n\n
                • Use rel=\"preconnect\"<\/code> and rel=\"preload\"<\/code> with parsimony and precision (preload only what is critical).<\/li>\n<\/ul>\n\n\n\n

                  Conclusion<\/h2>\n\n\n\n

                  The module Head Sorter<\/strong> brings order to the <head><\/code> of your WordPress site automatically, respecting good performance and technical SEO practices. Activate it, clear your caches, and enjoy cleaner, faster loading - without wasting time micromanaging tags.<\/p>","protected":false},"excerpt":{"rendered":"

                  WPMasterToolKit's Head Sorter module automatically optimizes the HTML header of your WordPress site by reorganizing the critical elements of the header. . This improves page loading speed and SEO without the need for additional configuration. Using PHP's DOMDocument library, it prioritizes important tags, contributing to better performance and an enriched user experience.<\/p>","protected":false},"featured_media":0,"parent":0,"template":"","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_surecart_dashboard_logo_width":"180px","_surecart_dashboard_show_logo":true,"_surecart_dashboard_navigation_orders":true,"_surecart_dashboard_navigation_invoices":true,"_surecart_dashboard_navigation_subscriptions":true,"_surecart_dashboard_navigation_downloads":true,"_surecart_dashboard_navigation_billing":true,"_surecart_dashboard_navigation_account":true},"class_list":["post-4826","module","type-module","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/wpmastertoolkit.com\/en\/wp-json\/wp\/v2\/module\/4826","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpmastertoolkit.com\/en\/wp-json\/wp\/v2\/module"}],"about":[{"href":"https:\/\/wpmastertoolkit.com\/en\/wp-json\/wp\/v2\/types\/module"}],"wp:attachment":[{"href":"https:\/\/wpmastertoolkit.com\/en\/wp-json\/wp\/v2\/media?parent=4826"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}