| 开发者 | featherr |
|---|---|
| 更新时间 | 2026年9月30日 20:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1.2 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
e- element family (Grid, Form, Tabs, Accordion, Background Video, Components and the rest). Elementor 4.1 and newer require WordPress 6.8; Feather itself runs on WordPress 6.0 and up.
Feather detects WP Rocket, LiteSpeed Cache, SiteGround Optimizer, W3 Total Cache, Imagify, Smush, and most other performance / image-optimizer plugins and lists them on the Settings screen, so you can leave overlapping toggles off where another plugin already does the work.
feather folder to the /wp-content/plugins/ directory, or install the plugin through the WordPress Plugins screen.Feather's defaults are conservative. Aggressive optimizations require a recent site scan and an explicit confirmation. Every change is reversible from the dashboard.
Yes. Feather detects them and shows which are active. Most Feather optimizations are Elementor-specific and don't overlap; where one does (JS defer, lazy-loading), leave it to whichever plugin you prefer.
No. Scans, metrics, and configuration all live on your server. The Lighthouse-on-demand feature uses your own Google PageSpeed Insights API key to call Google directly. Feather never proxies this through a third party.
Yes, in compatible mode (per-site configuration). Network-level controls are planned for a later release.
defer onto elementor-frontend-modules and elementor-frontend even when a non-deferred script depended on them, so those scripts ran before elementorModules existed. It now uses WordPress's loading-strategy API, which only defers a script when everything depending on it can wait. The atomic (v4) and Interactions scripts are covered too.loading="lazy" to exactly those, delaying hero videos and maps). It now only covers what core doesn't: comments, and Elementor templates and popups rendered outside the main content. It also respects the wp_lazy_loading_enabled filter.<img … /> tags no longer come out as <img … / width=… height=…> after "Auto-fix image dimensions".base-* / default-* stylesheets that load on every Elementor page.editor_events experiment off, unregisters the /elementor/v1/events/… proxy routes, and refuses any request Elementor's events code sends.elementor.red, where Elementor 4.x hosts its cloud template library.?ver= from Elementor asset URLs. That query string is Elementor's only cache-buster, so visitors kept stale CSS after every edit and, after an Elementor update, could get old JavaScript alongside the new. Elementor 4.3 rewrote frontend.min.js under the same URL.e- element or widget type), so future atomic elements are covered without a Feather update.elementor-v2-widgets-frontend, a handle Elementor no longer registers, while missing elementor-v2-action-link-handlers and elementor-v2-form-handlers. Both new handler bundles are now included, along with the tabs preview handler.elementor-post-{id}, not the elementor-post-css the gate looked for, so that CSS shipped on every non-Elementor request. The Kit stylesheet is deliberately left in place because themes inherit its global typography and colors.elementor-gf-*, elementor-gf-local-*) instead of two handles that no longer exist.elementor/ai/is_ai_enabled filter is gone from Elementor 4.x, so the feature relied on its dequeue fallback alone; it now answers the elementor_enable_ai user option at read time and covers all seven current AI bundles.e_optimized_assets_loading / e_lazyload / e_css_smooth_scroll sub-toggle, the e_element_cache sub-toggle, and "Trim Elementor frontend config payload" (the filter it hooked no longer exists). Their stored settings are cleaned up automatically on upgrade. The experiments card still forces Inline Font Icons and Optimized Markup, which are real.elementor-frontend-legacy, elementor-waypoints, elementor-animations, lottie-js, elementor/admin/menu/promotions, the Google Fonts preconnect detach). They matched nothing in Elementor 4.x and made the optimizations look broader than they were.admin_bar_menu lifecycle, so the previous priority-999 hook fired before the node was added and removed nothing. Switched to wp_before_admin_bar_render (which fires after all menu callbacks complete) and added a CSS belt-and-braces hide that guarantees the item never renders even if a third party re-adds the node after our removal.force_experiments, force_extra_experiments, element_cache) are now one feature card, "Force-enable Elementor performance experiments". Existing installs keep their behavior — sub-toggles for the extra experiments and element cache live under advanced.experiments.admin.php?page=feather, which produced a "Sorry, you are not allowed to access this page" error.complete, missing edge cases where the cached state briefly read as idle after the cron tick.wp_register_style() + wp_add_inline_style() instead of direct <style> echoes. Follows WordPress.org enqueue guidelines.load_plugin_textdomain() call. WordPress.org auto-loads translations for hosted plugins since WP 4.6.elementor-tabs-handler and elementor-youtube-handler on pages that don't use those atomic elements.get_style_depends() no longer leak error strings into Feather's asset map.Widget_WordPress class incorrectly declares Swiper as a dependency for every wp-widget-* type. Feather now strips that incorrect claim so sidebar widgets don't falsely require Swiper.