WP Meteor is a completely new mode of optimizing your page speed. Information technology works even on top of your existing optimizations, including:

  • Autoptimize
  • WP Rocket
  • WP Total Cache
  • WP Super Cache
  • LiteSpeed Cache

WP Shooting star is not compatible with:

  • Nitropack

WP Meteor is known to have delay bug with:

  • Elementor Offcanvas addon

Warning

The plugin might not work for someone, that's expected – delaying scripts has its downsides. Too, the plugin logics is quite complicated, so bugs happen.

If your site is business-critical or e-commerce, please exam advisedly all your business-critical pages, forms and/or your checkout process. Experience free to create an Effect if something doesn't work.

The plugin is made to get out no trace on the disk or in the database upon deactivation and removal, and then don't hesitate to install and test, may exist your site suits well for that kind of optimization.

Don't forget to test the site carefully after plugin installation. If you lot are not happy with the consequence – you can either uninstall the plugin, or create an Issue, I will either fix the trouble, or list a compatibility issue hither.

Ane MORE Warning

Infinite delay will delay your GA and GTM until user interaction. I would not recommed to use it, but information technology is nonetheless there because multiple users requested information technology. Use it with caution and at your ain risk.

HOW It WORKS

If user doesn't start interacting with page immediately, WP Meteor postpones loading and firing scripts until after page gets rendered, giving you lot 2x-5x boost in your Pagespeed metric.

This postponement in script loading profoundly improves perceived load times for your visitors. It also significantly improves the post-obit important SEO metrics:

  • Page Speed
  • Largest Contentful Paint (LCP)
  • Time To Interactive (TTI)
  • Full Blocking Time (TBT)

In May 2021, Google volition incorporate multiple page speed metrics every bit a search signal in the ranking algorythm

  1. Upload the plugin files to the /wp-content/plugins/wp-shooting star directory, or install the plugin through the WordPress plugins screen direct.
  2. Activate the plugin through the 'Plugins' screen in WordPress
  3. Use the Settings -> WP Meteor screen to configure the plugin

Is it skilful for SEO?

Yep, because all that matters is company experience, and WP Shooting star improves that experience with a lot faster load times

How can I easily compare speed with/without WP Meteor ?

Once WP Falling star is enabled, you can add ?wpmeteordisable query string parameter to a page URL in order to load the page without optimizations

How to exclude a page from optimization

Use wpmeteor_enabled filter and render false to completely disable WP Shooting star, example:

                      add_filter('wpmeteor_enabled', part ($value) {     global $post;     if ($mail && $mail service->ID == 1) {         return faux;     }     return $value; });

How to exclude a script from optimization

  1. Apply 'Exclude' tab to exclude scripts by matching src or inline content using regexp

  2. Use wpmeteor_exclude filter, which accepts 2 arguments: $exclude and $content. $content variable contains either src attribute, or text content of the script tag. Return true if you want to exclude the script. Case:

                              add_filter('wpmeteor_exclude', function ($exclude, $content) {     if (preg_match('/yourscript\.js/', $content)) {         return true;     }     return $exclude; }, null, 2);

Alternatively, you tin can utilize data-wpmeteor-nooptimize="true" script attribute to exclude it from optimization.

How to adjust filibuster exterior of 1s, 2s and Infinity

Use wpmeteor-frontend-adjust-wpmeteor filter in the following fashion:

                      add_filter('wp-falling star-frontend-adjust-wpmeteor', function ($wpmeteor, $settings) {     $wpmeteor['rdelay'] = 4000; // number of milliseconds to delay      return $wpmeteor; }, 100, 2);

i had been using amp to improve my site speed for a year or more. yet, it had compatibility issues that seemed evergreen and sometimes evernew. i uninstalled it and used cdn as well equally almost all wp enshroud and speed plugins to boost my site to no avail. luckily, i plant this plugin. it works all-time for me every bit it makes my website really really fast. my site ranks greenish on google folio speed insights, nigh always. my website address is flamesurfers.com.

Worked for me using Elementor, W3TC, and Ezoic.

Lots of Love for developers..

Help me a lot with page speed. Thank you!

Let me cutting to the chase. WP Meteror is an awesome plugin that really worked for me and rocketed my score up according to Google Folio Speed metrics. Furthermore, It is fully compatible with Autoptimize and WP Super Cache, 2 nifty plugins which I persistently consider among "must-haves." Being ever frustrated with GPS scores, I was always looking for a manner to minimize the damn "main thread piece of work," go rid of "return-blocking resources" and improve LCP, TTI and TBT (Ironically, Google still regards its own reCAPTCHA, Tag Director, etc. equally render-blocking or unused JavaScript!) The optimization of JS files and applying Defer attribute to scripts, among many others, only led to a slight improvement in my score, no way comparable with that of WP Meteor. Last but non to the lowest degree, using WP Shooting star had some downsides on my website as Alex had conspicuously explained. But at that place is an inbuilt exclusion session which helped me exclude troublesome scripts easily. In a nutshell, this plugin kills information technology on Page Speed and deserves 10 out of 5 stars!

Thank You So much it boosted my website speed about 25% thanks and keep up the Good Work

Read all 53 reviews

"WP Meteor Page Speed Optimization Topping" is open source software. The following people have contributed to this plugin.

Contributors

  • Aleksandr Guidrevitch

two.3.10 – WP Fastest Cache compatibility
2.three.9 – Regexp exlusions fixed
2.3.eight – outcome queue should not be processed if script loading is in progress Issue
two.three.vii – defer converted to data-defer for standards compliance
2.three.6 – Back up for missing tag
2.iii.v – Amend readyState management
2.three.4 – Lazy Images past Jetpack support added
2.iii.iii – Compatibility with PhastPress if 'Load scripts asynchronously' is disabled
2.iii.2 – Support for unquoted src and blazon script attributes
two.three.ane – Images lazyloading fixed for Swift Performance
2.3.0 – window messaging back up added, multiple improvements into effect treatment
2.ii.21 – Swift Performance support added
ii.ii.twenty – Breeze support added
2.2.xix – jQueryMock returned, to burn jQuery.fix early on
2.2.eighteen – minor fixes
2.2.17 – document.write at present properly processes inserted scripts
two.2.16 – amend AJAX calls detection
two.2.15 – better readyState tracking, getting rid of jQueryMock
ii.two.14 – Support for onreadystatechange property of document
2.two.13 – Bugfix in consequence queue management introduced in ii.two.12
2.2.12 – Of import bugfix in event queue direction
two.2.11 – Meta Slider support and general compatibility improvements
ii.2.10 – Bugfix
ii.2.9 – Bugfix
two.2.eight – Memory usage optimization
ii.ii.7 – Elementor error stock-still
two.2.6 – Newrelic forced exclusion
two.2.five – Avada Theme compatibility
2.two.4 – Swift Functioning compatibility
2.two.3 – Readme updated
ii.2.ii – CloudFlare RocketLoader compatibility Consequence stock-still
2.2.1 – Result fixed
2.2.0 – UI to exclude scripts
2.1.4 – Tracking for natively lazyloaded images improved
ii.1.3 – Getting rid of built-in lazyload handling in favor of native 1. Refactoring
2.ane.2 – Cloudflare Rocket Loader compatibility fixes
2.one.i – Backend support for wpmeteor_exclude filter, also fixes Fast Velocity css preload in a different mode Issue
two.1.0 – Event redispatching improved, compatibility fixes, refactoring
two.0.5 – Better Fast Velocity Minify compatibility
2.0.4 – Small CSS rewriting fix
2.0.iii – Support for onload properties of window, document and body Issue
2.0.2 – Support for onload events in Outcome
2.0.1 – Rewrite inside script tags fixed Issue
ii.0.0 – Major script loading logics update
1.5.seven – Missing files added
1.5.six – Moving before code to suit to Spider web Vitals all-time practices Consequence
one.v.five – Skip rewrite of content, other than text/html
1.5.4 – Improved detection of CloudFlare, better/safer script rewrites, dropping support for rocket_buffer
1.5.3 – SEOPress sitemaps.xml prepare Issue
one.5.ii – Forestall clicks during touchmove, RTL support added
ane.5.i – Emulate Elementor Powerpack Pro menu
i.5.0 – wpmeteor_enabled filter added, to allow to disable optimizations ocasionally
one.4.ix – document.write override immune for those who know how to do it better (egDivi editor)
i.4.viii – Divi theme builder compatibility fixed
ane.4.vii – SiteGround Optimizer + WP Rocket issue fixed
1.4.6 – Elementor Offcanvas double animation fix Consequence
i.4.v – Elementor Offcanvas animations suppressed Issue
1.4.4 – Elementor Entrance Animations bug stock-still
one.4.3 – Elementor Entrance Animations back up added
i.4.2 – Removed override for currentTarget for replayed events, fixes some navigation menus
1.4.i – For WP Rocket compatibility, using rocket_buffer filter to inject javascript
1.4.0 – Getting rid of { passive: truthful } for replayed pointer events
i.3.9 – DOMContentLoaded propagation to window object, proper effect handler bindings
1.3.eight – Improve fronted detection to avert rewriting AJAX and REST requests
1.3.7 – Proper contexts for domcontentloaded and window.onload outcome handlers
i.3.half dozen – Meliorate jQuery.prepare handling
ane.iii.v – CookieBot compatibility Issue fixed
1.3.four – Stopping click propagation when capturing events Outcome
1.three.iii – Better script loading in Firefox, scripts with both src and inline loading fixed Issue
1.3.ii – Improve delayed events for mobile Issue
1.3.ane – Click handling in mobile safari improved Event
1.3.0 – Gutenberg salve failure stock-still
1.2.9 – jQuery mockup stock-still to support window.load inside prepare() function
1.ii.8 – Bug breaking header tags stock-still
1.two.vii – Phastpress compatibility dropped
ane.two.6 – Small improvement to fire domcontentloaded and window.onload for non-optimized scripts
one.2.five – Support for Autoptimize native lazyload
i.2.iv – Delayed click/mouseover/mouseout events support added
1.two.3 – Native WP Rocket lazyload support
1.2.ii – Phastpress compatibility
1.2.1 – stripped lazysizes added in, with bgsizes plugin
1.2.0 – minor cleanup
ane.1.9 – simple lazyload polyfill
1.1.eight – infinite delay added
1.1.7 – rewriting redone to support Google AMP and other plugins that initialize late
1.ane.6 – working support Beaver Builder / Edit Mode
1.1.v – working support Elementor / Edit Fashion, Google AMP, AMP for WP
1.1.4 – back up for Elementor / Edit Mode
one.1.3 – support for AMP for WP plugin added
1.one.2 – back up for Google AMP plugin added
1.1.ane – readme.txt updated, warning added that information technology might not work for someone
1.1.0 – JetPack compatibility fixes
one.0.9 – ?wpmeteornopreload added to allow testing disabling preload
1.0.8 – data-cfasync="false" added to optimized scripts if backside CloudFlare
1.0.seven – ?wpmeteorcfasync parameter added to test disabling CloudFlare optimizations
1.0.6 – another iteration on domcontentloaded and window.onload handlers, jQuery mock rewrite
ane.0.5 – amend treatment for broken domcontentloaded and window.onload handlers, better jQuery mock
1.0.iv – ameliorate cleanup on plugin deactivation
one.0.iii – readme.txt updated
1.0.2 – readme.txt updated
ane.0.1 – minor Settings panel improvements
1.0.0 – initial release