Custom Header Extended vs Image Prioritizer

A plugin for allowing users to set a custom header on a per-post basis. This plugin hooks into the WordPress custom-header theme feature and overwrites the values on single post views if the post has been given a custom header. Features This plugin creates a custom meta box on the edit post screen. From that point, you can select a custom header image. You can also select whether to display your header text and its color if your theme supports that option. The options you choose will be shown on the single post page on the front end. Requirements Your theme must support the core WordPress implementation of the Custom Headers theme feature. Professional Support If you need professional plugin support from me, the plugin author, you can access the support forums at Theme Hybrid, which is a professional WordPress help/support site where I handle support for all my plugins and themes for a community of 40,000+ users (and growing). Plugin Development If you’re a plugin author or just a code hobbyist, you can follow the development of this plugin on it’s GitHub repository. Donations Yes, I do accept donations. If you want to buy me a beer or whatever, you can do so from my donations page. I appreciate all donations, no matter the size. Further development of this plugin is not contingent on donations, but they are always a nice incentive.

This plugin optimizes the loading of images (and videos) with prioritization to improve Largest Contentful Paint (LCP), lazy loading, and more accurate image size selection. The current optimizations include: Add breakpoint-specific fetchpriority=high preload links (both as LINK[rel=preload] elements and Link response headers) for image URLs of LCP elements: An IMG element, including the srcset/sizes attributes supplied as imagesrcset/imagesizes on the LINK. The first SOURCE element with a type attribute in a PICTURE element. (Art-directed PICTURE elements using media queries are not supported.) An element with a CSS background-image inline style attribute. An element with a CSS background-image applied with a stylesheet (when the image is from an allowed origin). A VIDEO element’s poster image. Ensure fetchpriority=high is only added to an IMG when it is the LCP element across all responsive breakpoints. Add fetchpriority=low to IMG tags which appear in the initial viewport but are not visible, such as when they are subsequent carousel slides. Lazy loading: Apply lazy loading to IMG tags based on whether they appear in any breakpoint’s initial viewport. Implement lazy loading of CSS background images added via inline style attributes. Lazy-load VIDEO tags by setting the appropriate attributes based on whether they appear in the initial viewport. If a VIDEO is the LCP element, it gets preload=auto; if it is in an initial viewport, the preload=metadata default is left; if it is not in an initial viewport, it gets preload=none. Lazy-loaded videos also get initial preload, autoplay, and poster attributes restored when the VIDEO is going to enter the viewport. Responsive image sizes: Ensure sizes=auto is set on IMG tags after setting correct lazy-loading (above). ~~Compute the sizes attribute using the widths of an image collected from URL Metrics for each breakpoint (when not lazy-loaded since then handled by sizes=auto).~~ (This has been removed due to an issue; use Enhanced Responsive Images instead.) Reduce the size of the poster image of a VIDEO from full size to the size appropriate for the maximum width of the video (on desktop). This plugin requires the Optimization Detective plugin as a dependency. Please refer to that plugin for additional background on how this plugin works as well as additional developer options. 👉 Note: This plugin optimizes pages for actual visitors, and it depends on visitors to optimize pages. As such, you won’t see optimizations applied immediately after activating the plugin. Please wait for URL Metrics to be gathered for both mobile and desktop visits. And since administrator users are not normal visitors typically, optimizations are not applied for admins by default. Your site must have the REST API accessible to unauthenticated frontend visitors since this is how metrics are collected about how a page should be optimized. There are currently no settings and no user interface for this plugin since it is designed to work without any configuration.