Empirical Responsive Images – Auto Image Sizes, WebP & AVIF
| 开发者 | jesusinica |
|---|---|
| 更新时间 | 2026年11月3日 05:05 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- A small browser check compares each displayed image with the sizes already available. Images with a good match are ignored.
- Missing sizes are confirmed before any work is scheduled.
- WordPress creates the new image files later, as a background task.
- Your existing responsive image markup picks them up, and your cache refreshes.
- Future visitors get a closer image size.
- Better-sized responsive images for phones, tablets, laptops, and high-density screens.
- Missing WordPress thumbnails created automatically, so there is no need to regenerate thumbnails for your whole library.
- WebP and AVIF versions when your server supports them.
- Better
srcsetandsizeschoices through normal WordPress markup. - Coverage for Media Library images and manageable local theme and plugin images.
- Automatic cache refresh after new image files are ready.
- Status tables under Tools > Responsive Images, if you are curious. Nothing there needs your attention.
安装:
- In WordPress, go to Plugins > Add New and search for Empirical Responsive Images.
- Click Install Now, then Activate.
- That's it. There is no setup step.
屏幕截图:
常见问题:
Do I need to configure anything?
No. Install it, activate it, and you are done. It learns, creates sizes, retries when necessary, and refreshes your cache on its own. The settings under Tools > Responsive Images are optional.
Do I need to approve every new size?
No. Confirmed gaps are queued, created, and used automatically. The administration page shows progress; it is not an approval queue.
Do I need to regenerate thumbnails?
No. The plugin creates the missing sizes your pages actually use, one image at a time, in the background. If you prefer to run a rebuild yourself, the optional WP-CLI commands can do it.
How long until I see results?
Pages that get regular traffic are usually first. Regular visitors confirm a missing size across three separate 15-minute periods by default, and the plugin runs up to 50 image jobs per day, so large sites catch up gradually. Pages with few visitors take longer.
Can this improve "Improve image delivery" or "Properly size images" in PageSpeed Insights?
It can help when PageSpeed finds images that are much larger than the space where they appear. The plugin creates closer size choices and can add WebP/AVIF versions. It does not heavily compress original images or turn animated GIFs into videos, so some recommendations may remain. One test page improved from 75 to 99 and its Largest Contentful Paint (LCP) improved from 7.2 seconds to 2.3 seconds. Scores vary; no PageSpeed or Core Web Vitals result is guaranteed.
Does it convert images to WebP and AVIF?
Yes, when your server's image library supports the format. It keeps your originals and adds separate WebP/AVIF files.
Is this different from an image compression plugin?
Yes. Compression plugins mainly make image files smaller. Empirical Responsive Images mainly creates the image dimensions your layouts need. Both jobs can be useful.
Can I use it with another image optimization plugin?
Usually. Let the other plugin compress originals and let this plugin create responsive sizes. If both plugins create WebP/AVIF versions, enable that feature in only one. Test the combination on a copy of your site before using it on a live store or busy site.
Does it work with caching plugins and CDNs?
The plugin can refresh caches from WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, Breeze, Autoptimize, and SiteGround Speed Optimizer after creating images. It can still learn WordPress images when a CDN changes their public URLs. If a separate CDN keeps its own page cache, that CDN or its WordPress plugin must also clear the cached page.
Does it work with lazy loading, page builders, and WooCommerce?
Usually, when they produce normal WordPress image elements. The plugin rechecks lazy images after they load and watches images added after the page opens. When a gallery, slider, or WooCommerce product variation swaps a wrapped image, its WebP/AVIF sources step aside so the new image shows. CSS background images, drawing canvases, remote images, and heavily customized JavaScript galleries may not be eligible.
Will it slow down visitors?
Image checks run during spare browser time. Missing files are created later by WordPress background tasks. Visitors do not wait for resizing or WebP/AVIF generation.
Do logged-in users need the same repeated visits?
Subscribers do. By default, a logged-in Contributor, Author, Editor, or Administrator can confirm a valid missing size sooner.
What visitor information is collected?
Only a secure code pointing to a local image and rounded size information needed to find a missing choice. The plugin does not store a visitor's identity, IP address, browser details, referring page, or the URL of the page they visited.
Can bots create endless image sizes?
No. Only marked local images and a fixed list of sizes are accepted. Near matches count as covered, and strict queue, retry, storage, and daily work limits keep generation bounded.
Will it work on my hosting?
Most standard WordPress hosts should work if uploads are writable, WordPress background tasks run normally, and the server can create the requested image format. If background tasks are disabled, queued work waits until the host runs them.
更新日志:
- Fewer server requests from visitors while the image queue is full: only one visitor in ten reports missing image sizes until the queue has room again. Logged-in editors still report every time.
- Faster page rendering: pages with many images spend about 70% less server time in the plugin.
- Images whose alt text or other attributes contain a ">" character are now processed, and no longer keep an internal marker attribute.
- Fix a fatal error with themes that pass an unexpected image ID to WordPress image functions.
- Stop damaged image or layout data saved in the database from breaking pages, regeneration or background work.
- Cap unusually large numbers in visitor reports so PHP 8.5 no longer logs warnings.
- New plugin name, icon, banner, and screenshots, plus a clearer description of how the plugin works on its own.
- Remove a redundant setting from the featured-image lookup used for cache refreshes.
- Fix WebP and AVIF images not showing on HTTPS sites whose uploads URL is stored with http. Picture sources now load over HTTPS whenever the page or the original image does, which stops browsers blocking them as mixed content. WooCommerce product galleries were one place this showed up.
- Stop repeat visitor reports from using up daily image work and refreshing pages when the image files and layout are already in place.
- Fix a full-site cache clear after background image work. Once new image sizes are ready, only the published post each image belongs to and posts using it as their featured image are refreshed; other pages pick up the new sizes when their cache expires. Sites with a long queue were cleared every night as the daily limit reset at midnight UTC.
- Fix galleries, sliders and product variation swaps that kept showing the original photo when the plugin had wrapped the image in a picture element. The WebP/AVIF sources now step aside while a script shows another image and return when the original comes back.
- Synchronize matching responsive image preloads, including WP Rocket hints, with current priority-image candidates. Preserve art-directed, format-specific and ambiguous hints.
- Preserve authored responsive sizes when upstream filters produce duplicate image attributes, avoiding competing oversized downloads.
- Delay upgrade cache purges until WordPress has loaded cache-plugin dependencies, preventing first-request failures with WP Rocket.
- Fix high-priority image learning that could generate a slightly undersized candidate the browser skips. New targets round upward, with existing queue and storage limits preserved.
- Keep cached version-2 image reports compatible during updates.
- Improve LCP image learning with static WebP support, tighter viable sizing for high-priority images, exact-width generation, and WP Rocket observer compatibility.
- Rewrite the public WordPress.org description and FAQs in plain language while preserving privacy details, compatibility guidance, and performance caveats.