WP Meteor Website Speed Optimization Addon

Descripción

WP Meteor ofrece una forma original de optimizar aún más la velocidad de tu sitio web. Con este plugin puedes aumentar tu puntuación de PageSpeed hasta 5 veces.
El plugin es 100% gratuito, es compatible y funciona bien con la mayoría de los plugins de caché populares como:
* Autoptimize
* WP Rocket
* WP Total Cache
* WP Super Cache
* Phastpress
* LiteSpeed
* Hummingbird
* WP Fastest Cache
* SiteGround Optimizer

También funciona bien con maquetadores web como Elementor o con optimizadores de imágenes como ShortPixel.

Las pocas incompatibilidades conocidas se enumeran en las FAQ.

VENTAJAS

WP Meteor puede mejorar los resultados de Pagespeed y el tiempo de carga real de tu web hasta 5 veces más. No tienes que creernos, solo tardarás 2 minutos en instalar el plugin y comprobar cómo mejora la velocidad de tu web.
Y dado que el plugin está diseñado para no dejar rastro en tu disco duro o base de datos cuando se desactiva y se elimina, no hay ningún riesgo para ti.

CÓMO FUNCIONA

Si el usuario no interactúa con la página inmediatamente, WP Meteor aplaza la carga y el disparo de scripts hasta que la página se haya mostrado, lo que aumenta la métrica de velocidad de la página, de media, en 2 a 5 veces.

Este retraso en la carga de los scripts mejora enormemente los tiempos de carga percibidos por tus visitantes. También mejora significativamente las siguientes importantes métricas de SEO:

ACELERA AÚN MÁS TU WEB

Si quieres optimizar la velocidad de tu web al máximo de forma automática, asegurándote de que se atiendan todos los Core Web Vitals, te recomendamos probar FastPixel.io de forma gratuita.
El proyecto FastPixel es una colaboración entre el creador de WP Meteor y ShortPixel, y soluciona, con solo unos clics, todos los problemas comunes que afectan a los Core Web Vitals.

Instalación

  1. Sube los archivos del plugin al directorio «/wp-content/plugins/wp-meteor», o instala el plugin directamente desde la pantalla de plugins de WordPress.
  2. Activa el plugin en la pantalla «Plugins» en WordPress.
  3. Configure el plugin a través de la pantalla de ajustes -> WP Meteor.

FAQ

¿Se puede utilizar este plugin en cualquier web?

Aunque el plugin puede no ser compatible con todas las configuraciones, es importante tener en cuenta que retrasar los guiones puede tener inconvenientes en algunos casos.

  • Para los sitios de misión crítica, recomendamos encarecidamente probar a fondo las páginas esenciales, los formularios y el proceso de pago. Si tienes algún problema, notifícalo creando un ticket de soporte.

  • Vale la pena mencionar que el plugin está diseñado para no dejar datos residuales en tu servidor o base de datos tras su desactivación y eliminación. Te invitamos a instalarlo y evaluar su idoneidad para optimizar tu sitio.

  • Después de instalar el plugin, te aconsejamos que realices una prueba completa del sitio. Si los resultados no cumplen tus expectativas, tienes la opción de desinstalar el plugin. Como alternativa, puedes explorar FastPixel Website Accelerator.

Problemas conocidos

  • WP Meteor no es compatible con Nitropack.
  • Además, se sabe que WP Meteor tiene problemas de retraso con la extensión de Elementor Offcanvas.
  • El uso de la opción «Retraso infinito» pospondrá la activación de Google Analytics (GA) y Google Tag Manager (GTM) hasta que haya interacción del usuario. Aunque ofrecemos esta opción debido a la demanda popular, no recomiendo su uso. Si decides utilizarla, por favor, ten precaución y ten en cuenta que lo haces bajo tu propio riesgo.

¿Cómo puedo comparar fácilmente la velocidad con/sin WP Meteor?

Una vez activado WP Meteor, puedes añadir el parámetro de cadena de consulta ?wpmeteordisable a la URL de una página para cargarla sin optimizaciones.

¿Cómo excluyo una página de la optimización?

Utiliza el filtro wpmeteor_enabled y devuelve false para desactivar WP Meteor por completo, como en este ejemplo:

add_filter(‘wpmeteor_enabled’, function ($value) {
global $post;
if ($post && $post-> ID == 1) {
return false;
}
return $value;
});

Cómo excluir un script de la optimización

  1. Utiliza la pestaña de Exclusiones para excluir scripts mediante la coincidencia de src o contenido integrado con expresiones regulares.
  2. Utiliza el filtro wpmeteor_exclude que acepta 2 argumentos: $exclude y $content. La variable $content contiene tanto el atributo src como el contenido de texto de la etiqueta script. Devuelve true si quieres excluir el script. Ejemplo:

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

Alternativamente, puedes utilizar el atributo de script data-wpmeteor-nooptimize=»true» para excluirlo de la optimización.

Cómo ajustar el retardo fuera de 1s, 2s e infinito

Utiliza el filtro wpmeteor-frontend-adjust-wpmeteor de la siguiente manera:

add_filter(‘wp-meteor-frontend-adjust-wpmeteor’, function ($wpmeteor, $settings) {
$wpmeteor[‘rdelay’] = 4000; // número de milisegundos para retrasar
return $wpmeteor;
}, 100, 2);

Reseñas

15 de mayo de 2024
The plugin works like a charm!I had a minor issue with a feature and I wrote the dev about it. Within a day he had updated to plugin to fix the issue.
26 de marzo de 2024
I’ve been working on improving the pagespeed performance for my site over the past few days. Pagespeed is always going to be a compromise. For Coder Sports we need to provide parents with information on our learn to code programs in a fun interactive format, including responsive mobile. After running the fantastic Jetpack boost along with redis and multiple efforts to optimize the homepage, I was expecting much from adding WP meteor – But wow was I wrong! This simple to install and run plugin added 10 – 20 points to our mobile pagespeed insights score on a consistent basis, granted it was a low bar, but still, very impressive. I found that the infinite delay for LCP worked fine for my site and provided the best «bang for the buck».
19 de enero de 2024
Issue with microsoft edge browser. SCRIPT1005: SCRIPT1005: Expected ‘(‘ SCRIPT1002: SCRIPT1002: Syntax error
17 de noviembre de 2023
did it work? yes. did it also make my mobile pages unresponsive? yes I have google maps with my own api, and it works fine without the plugin but with the plugin on mobile it completly crashes the brower and makes it freeze. i tried everything to exclude it but still no luck
20 de septiembre de 2023
i have a rare bug when i active this plugin, when is active, my normal images does not load at all, only when i’m logged :/, when you access to the Page as not logged user, this does not load the images, you have an idea what can be the problem ? Sorry for my bad english
Leer todas las 75 reseñas

Colaboradores y desarrolladores

«WP Meteor Website Speed Optimization Addon» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«WP Meteor Website Speed Optimization Addon» está traducido en 2 idiomas. Gracias a los traductores por sus contribuciones.

Traduce «WP Meteor Website Speed Optimization Addon» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

3.4.3 – Major improvement, script unblocking rewritten using inplace modifications. Hopefully, addresses Bug
3.4.2 – Minor, updating links to FastPixel Website Accelerator as it is now live in WordPress Plugin directory
3.4.1 – Better compatibility with Smush, backport optimization code from FastPixel Website Accelerator
3.4.0 – Javascript runner sync with Fastpixel Acceleration FastPixel Website Accelerator
3.3.3 – links improved
3.3.2 – readme.txt updated
3.3.1 – Support for WP Fastest Cache and SiteGround Optimizer returned, but not guaranteed to work
3.3.0 – Interaction with caching plugins reworked
3.2.6 – Added https://legalblink.it/ GDPR banner to exclude
3.2.5 – Fix for jQuery being excluded from optimization (e.g. by Phastpress)
3.2.4 – Fix for is_plugin_active not being available Issue
3.2.3 – bug fix
3.2.2 – better compatibility with LiteSpeed cache
3.2.1 – support for automatic exclusion of GDPR/cookie banners, try to reduce blocking time when inserting scripts
3.2.0 – Migration to external wp-meteor javascript library, added support for shadow root inserted scripts to address issue
3.1.9 – Migration to esbuild to generate javascript with smaller footprint, upgrade wp-notice library to fix CSRF perfmanently
3.1.8 – jQuery mock improved
3.1.7 – problem fixed
3.1.6 – issue fixed, PHP 8.2+ compatibility fixed
3.1.5 – Speed improvements, blocking time reduction, CSRF security fix for wp-notice library CVE-2023-26543
3.1.4 – Maintain optimization of Avada’s lazysizes.js as it depends on jQuery
3.1.3 – Problem cleanup only on uninstallation
3.1.2 – Visual Builders compatibility improvements
3.1.1 – removed lazySizesConfig from optimization
3.1.0 – fixed document.write, improvements in loading scripts and pre-binding
3.0.9 – bug fixes released
3.0.8 – bug fixes for feature released in 3.0.6
3.0.7 – Script removal improved to make third-party scripts happy, willing to remove scripts themselves
3.0.6 – bugfix release, support for onload attributes
3.0.5 – possibility to remove comments
3.0.4 – Problem fixed, wp-login.php is excluded from optimization
3.0.3 – issue fixed, support for modules restored
3.0.2 – Problem partially fixed
3.0.1 – Problem fixed, body onload tag handling added to fix «wordpress social login» plugin and probably others
3.0.0 – Several improvements:
* Zero-delay mode.
* Improvements in forwarding events to third-party scripts loaded via GTM
* Integration of script exclusions with Autoptimize, WP Rocket and Breeze
* Improved detection when loading assets.
* Support for late events fixed
* Support for privacy services, specifically tested for OneTrust
2.3.10 – WP Fastest Cache compatibility
2.3.9 – Regexp exclusions fixed
2.3.8 – Event queue should not be processed when script loading is in progress Issue
2.3.7 – defer converted to data-defer to comply with standards
2.3.6 – support for missing tag
2.3.5 – Better readyState management
2.3.4 – added lazy images by Jetpack support
2.3.3 – Compatibility with PhastPress when ‘Load scripts asynchronously’ is disabled
2.3.2 – Support for script attributes without quotes src and type
2.3.1 – Fixed lazyloading of images for [Swift Performance] (https://wordpress.org/plugins/swift-performance-lite/)
2.3.0 – added support for window messaging, several improvements in event handling
2.2.21 – added Swift Performance support
2.2.20 – added support for Breeze
2.2.19 – jQueryMock returned to trigger jQuery.ready early
2.2.18 – minor fixes
2.2.17 – document.write now correctly processes inserted scripts
2.2.16 – better detection of AJAX calls
2.2.15 – better tracking of readyState, removal of jQueryMock
2.2.14 – support for onreadystatechange property of document
2.2.13 – Bugfix in event queue management, introduced in 2.2.12
2.2.12 – important bugfix in event queue management
2.2.11 – Meta Slider support and general compatibility improvements
2.2.10 – Bug fix
2.2.9 – bug fix
2.2.8 – Memory usage optimization
2.2.7 – Elementor bug fixed
2.2.6 – Newrelic forced exclusion
2.2.5 – Avada theme compatibility
2.2.4 – Swift performance compatibility
2.2.3 – Readme updated
2.2.2 – CloudFlare RocketLoader compatibility [issue](https://wordpress.org/support/topic/not-clickable-menu-links-and-products/
2.2.1 – Problem fixed
2.2.0 – UI to exclude scripts
2.1.4 – improved tracking for natively slowed down images
2.1.3 – Abolish built-in lazyload handling in favor of native. Refactoring.
2.1.2 – Cloudflare Rocket Loader compatibility fixed
2.1.1 – Backend support for wpmeteor_exclude filter, also fix Fast Velocity css preload in a different way Issue
2.1.0 – Event redispatching improved, compatibility fixes, refactoring
2.0.5 – Better Fast Velocity Minify compatibility
2.0.4 – Minor fix for CSS rewriting
2.0.3 – Support for onload properties of window, document and body Issue
2.0.2 – support for onload events in Issue
2.0.1 – fixed rewriting inside script tags Issue
2.0.0 – Major update of script load logic
1.5.7 – Added missing files
1.5.6 – Moved previous code to align with Web Vitals best practices Issue
1.5.5 – Skipped rewriting content that is not text/html
1.5.4 – Improved CloudFlare detection, better/safer script rewrites, removal of support for rocket_buffer
1.5.3 – SEOPress sitemaps.xml fixed Issue
1.5.2 – Prevent clicks on touchmove, RTL support added
1.5.1 – Elementor Powerpack Pro menu emulation
1.5.0 – added wpmeteor_enabled filter to disable optimizations occasionally
1.4.9 – document.write override allowed for those who know how to do it better (e.g. Divi Editor)
1.4.8 – Divi Theme Builder compatibility fixed
1.4.7 – SiteGround Optimizer + WP Rocket issue fixed
1.4.6 – Elementor Offcanvas double animation fixed issue
1.4.5 – Elementor Offcanvas animations suppressed issue
1.4.4 – fixed problems with Elementor input animations
1.4.3 – added support for Elementor input animations
1.4.2 – Removed override for currentTarget on repeated events, fixed some navigation menus
1.4.1 – For WP Rocket compatibility, use rocket_buffer filter to include javascript
1.4.0 – Elimination of { passive: true } for replayed pointer events
1.3.9 – DOMContentLoaded passing to the window object, correct event handler bindings
1.3.8 – Better fronted detection to avoid rewriting AJAX and REST requests
1.3.7 – Correct contexts for domcontentloaded and window.onload event handlers
1.3.6 – Better handling of jQuery.ready
1.3.5 – Fixed CookieBot compatibility [issue] (https://wordpress.org/support/topic/error-with-my-website-2/)
1.3.4 – Stop click forwarding when capturing events issue
1.3.3 – Better script loading in Firefox, fixed scripts with src and inline loading Issue
1.3.2 – Better delayed events for mobile devices Issue
1.3.1 – Improved click handling in mobile Safari Issue
1.3.0 – Gutenberg memory bug fixed
1.2.9 – fixed jQuery mockup to support window.load inside ready() function
1.2.8 – fixed header tag breaking bug
1.2.7 – Phastpress compatibility removed
1.2.6 – Minor improvement when triggering domcontentloaded and window.onload for non-optimized scripts
1.2.5 – Support for autoptimize native lazyload
1.2.4 – added support for delayed click/mouseover/mouseout events
1.2.3 – Added native support for WP Rocket lazyload
1.2.2 – added phastpress compatibility
1.2.1 – added stripped lazysizes, using bgsizes plugin
1.2.0 – minor cleanup
1.1.9 – simple lazyload polyfill
1.1.8 – added infinite delay
1.1.7 – rewriting reworked to support Google AMP and other plugins that initialize late
1.1.6 – working support for Beaver Builder / Edit Mode
1.1.5 – working support for Elementor / Edit Mode, Google AMP, AMP for WP
1.1.4 – support for Elementor / Edit Mode
1.1.3 – added support for AMP for WP plugin
1.1.2 – added support for Google AMP plugin
1.1.1 – readme.txt updated, added warning that it might not work for someone
1.1.0 – JetPack compatibility fixed
1.0.9 – added ?wpmeteornopreload to test preload disabling
1.0.8 – added data-cfasync=»false» to optimize scripts if they are behind CloudFlare
1.0.7 – added ?wpmeteorcfasync parameter to test disabling CloudFlare optimizations
1.0.6 – further iteration of domcontentloaded and window.onload handlers, jQuery mock rewrite
1.0.5 – better handling for broken domcontentloaded and window.onload handlers, better jQuery mock
1.0.4 – better cleanup on plugin deactivation
1.0.3 – readme.txt updated
1.0.2 – readme.txt updated
1.0.1 – minor Settings panel improvements
1.0.0 – initial release