Easy SwipeBox vs Image Prioritizer

Easy SwipeBox plugin for WordPress websites gives you a flexible, aesthetic and mobile-friendly Lightbox solution for just about all media links on your website. Easy SwipeBox uses the packed SwipeBox and is multisite compatible. Main features Enqueuing of SwipeBox Javascript and CSS files. Customization of SwipeBox lightbox appereance and behaviour from the Lightbox Settings page. Autodetection of links to images or videos. You can exclude/include media types from the Autodetection Settings page. Other geek settings in the Advanced Settings page. Autodetection Select one or more options from Autodetection setting page, Easy SwipeBox automatically detects the media type and add class="swipebox" to their links. Otherwise, add class="swipebox" yourself to make the magic happen. If you like to exclude some images or videos from autodetection enter the selector that groups these elements. By default, Easy SwipeBox uses .no-swipebox. Contribution There are many ways to contribute to this plugin: Report a bug, submit pull request or new feature proposal: visit the Github repo. Translate it in your language: visit the WordPress translation page. Rate it 5 stars on WordPress.org. Buy me a beer! Support Need help? Read the FAQ or visit the WordPress.org support page / Github Issue Tracker. Note: this plugin use SwipeBox jQuery plugin as Lightbox solution. For any issues and pull requests related to SwipeBox functionalities please visit the SwipeBox Repo.

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.