Autoptimize

Descripción

Autoptimize makes optimizing your site really easy. It can aggregate, minify and cache scripts and styles, injects CSS in the page head by default but can also inline critical CSS and defer the aggregated full CSS, moves and defers scripts to the footer and minifies HTML. You can optimize and lazy-load images, optimize Google Fonts, async non-aggregated JavaScript, remove WordPress core emoji cruft and more. As such it can improve your site’s performance even when already on HTTP/2! There is extensive API available to enable you to tailor Autoptimize to each and every site’s specific needs.
If you consider performance important, you really should use one of the many caching plugins to do page caching. Some good candidates to complement Autoptimize that way are e.g. Speed Booster pack, KeyCDN’s Cache Enabler, WP Super Cache or if you use Cloudflare WP Cloudflare Super Page Cache.

Soporte premium
Proporcionamos excelentes servicios de soporte de Autoptimize Pro y de optimización de rendimiento web, ¡revisa nuestra oferta en https://autoptimize.com/!

(La imagen Speed-surfing tiene licencia creative commons de LL Twistiti)

Instalación

Sólo instálalo desde la pantalla de «Plugins > Añadir nuevo» de tu WordPress y estará hecho. La instalación manual también es muy sencilla:

  1. Sube el archivo zip y descomprímelo en el directorio /wp-content/plugins/
  2. Activa el plugin desde el menú ‘Plugins’ de WordPress
  3. Ve a Ajustes > Autoptimize y activa las opciones que quieras. Generalmente esto significa «Optimizar HTML/ CSS/ JavaScript».

FAQ

¿Qué hace el plugin para ayudar a la velocidad de mi sitio?

Concatena todos los scripts y estilos, los minimiza y comprime, añade caducidad a las cabeceras y luego las almacena en caché, mueve los estilos a la cabecera de la página y scripts (opcional) al pie de página. También minimiza el código HTML, haciendo que tu página sea realmente ligera.

Pero tengo HTTP/2, entonces ¿no necesito usar Autoptimize?

Sin duda, HTTP/2 es un gran paso adelante, ya que reduce significativamente el impacto de múltiples solicitudes del mismo servidor al utilizar la misma conexión para realizar varias solicitudes simultáneas. Dicho esto, combinar CSS y JS todavía puede tener mucho sentido, como se describe en este artículo de css-tricks.com y esta entrada de blog de uno de los ingenieros de eBay. La conclusión: configurar, probar, reconfigurar, volver a probar, retocar y ver qué funciona mejor en tu contexto. Tal vez solo necesites HTTP/2, tal vez HTTP/2 más combinar y minimizar, tal vez HTTP/2 y minimizar (algo que Autoptimize también puede hacer, simplemente desmarca las opciones «combinar archivos JS» y/o «combinar archivos CSS»). Por último, Autoptimize puede hacer mucho más que «solo» optimizar tu JS y CSS por supuesto 😉

¿Esto funcionará con mi blog?

Si bien Autoptimize no ofrece ninguna garantía, en general funcionará perfectamente si lo configuras correctamente. Consulta «Diagnosticar problemas» más abajo para obtener información sobre cómo configurar en caso de problemas.

¿Por qué el archivo «jquery.js» no está optimizado?

A partir de Autoptimize versión 2.1, el archivo «jquery.js» del núcleo de WordPress no está optimizado por la sencilla razón de que muchos plugins populares inyectan JavaScript integrado que no se combina (debido a posibles problemas de tamaño de caché con código JavaScript integrado) y que confía en que jQuery se encuentre disponible; por lo que excluir el archivo «jquery.js» asegura que funcionen la mayoría de los sitios. Si también deseas optimizar jQuery, puedes eliminarlo de la lista de exclusión de la optimización de JavaScript (es posible que tengas que activar «añadir también JavaScript integrado» o cambiar a «forzar JavaScript en la cabecera»).

Why is Autoptimized JS render blocking?

If not “forced in head”, Autoptimized JS is not render blocking as it has the “defer” flag added. It is however possible another plugin removes the “defer”-flag. Speed Booster Pack was reported doing this, but the behavior has not been confirmed yet.

Why is the autoptimized CSS still called out as render blocking?

With the default Autoptimize configuration the CSS is linked in the head, which is a safe default but has Google PageSpeed Insights complaining. You can look into “inline all CSS” (easy) or “inline and defer CSS” (better) which are explained in this FAQ as well.

¿Cuál es el uso de «Incrustar y retrasar CSS»?

CSS in general should go in the head of the document. Recently a.o. Google started promoting deferring non-essential CSS, while inlining those styles needed to build the page above the fold. This is especially important to render pages as quickly as possible on mobile devices. As from Autoptimize 1.9.0 this is easy; select “inline and defer CSS”, paste the block of “above the fold CSS” in the input field (text area) and you’re good to go!

¿Pero cómo uno puede averiguar cuál es el CSS «antes de hacer scroll»?

There’s no easy solution for that as “above the fold” depends on where the fold is, which in turn depends on screensize. There are some tools available however, which try to identify just what is “above the fold”. This list of tools is a great starting point. The Sitelocity critical CSS generator and Jonas Ohlsson’s criticalpathcssgenerator are nice basic solutions and http://criticalcss.com/ is a premium solution by the same Jonas Ohlsson. Alternatively this bookmarklet (Chrome-only) can be helpful as well.

¿O deberías poner incrustado todo el CSS?

The short answer: probably not. Although inlining all CSS will make the CSS non-render blocking, it will result in your base HTML-page getting significantly bigger thus requiring more “roundtrip times”. Moreover when considering multiple pages being requested in a browsing session the inline CSS is sent over each time, whereas when not inlined it would be served from cache. Finally the inlined CSS will push the meta-tags in the HTML down to a position where Facebook or Whatsapp might not look for it any more, breaking e.g. thumbnails when sharing on these platforms.

Mi caché es cada vez más grande, ¿no vacía Autoptimize la caché?

Autoptimize does not have its proper cache purging mechanism, as this could remove optimized CSS/JS which is still referred to in other caches, which would break your site. Moreover a fast growing cache is an indication of other problems you should avoid.

Instead you can keep the cache size at an acceptable level by either:

  • disactivating the “aggregate inline JS” and/ or “aggregate inline CSS” options
  • excluding JS-variables (or sometimes CSS-selectors) that change on a per page (or per pageload) basis. You can read how you can do that in this blogpost.

Despite above objections, there are 3rd party solutions to automatically purge the AO cache, e.g. using this code or this plugin, but for reasons above these are to be used only if you really know what you’re doing.

¿«Vaciar la caché» parece no funcionar?

When clicking the “Delete Cache” link in the Autoptimize dropdown in the admin toolbar, you might to get a “Your cache might not have been purged successfully”. In that case go to Autoptimizes setting page and click the “Save changes & clear cache”-button.

Además, no te preocupes si tu caché nunca baja de 0 archivos/ 0KB, ya que Autoptimize (a partir de la versión 2.2) precargará automáticamente la caché inmediatamente después de haberla limpiado para acelerar significativamente la minimización.

¡Mi sitio aparece roto cuando purgo la caché de Autoptimize!

When clearing AO’s cache, no page cache should contain pages (HTML) that refers to the removed optimized CSS/ JS. Although for that purpose there is integration between Autoptimize and some page caches, this integration does not cover 100% of setups so you might need to purge your page cache manually.

¿Puedo seguir usando Rocket Loader de Cloudflare?

Cloudflare Rocket Loader is a pretty advanced but invasive way to make JavaScript non-render-blocking, which Cloudflare still considers Beta. Sometimes Autoptimize & Rocket Loader work together, sometimes they don’t. The best approach is to disable Rocket Loader, configure Autoptimize and re-enable Rocket Loader (if you think it can help) after that and test if everything still works.

At the moment (June 2017) it seems RocketLoader might break AO’s “inline & defer CSS”, which is based on Filamentgroup’s loadCSS, resulting in the deferred CSS not loading.

He probado Autoptimize pero mi puntuación de Google PageSpeed apenas ha mejorado

Autoptimize is not a simple “fix my Pagespeed-problems” plugin; it “only” aggregates & minifies (local) JS & CSS and images and allows for some nice extra’s as removing Google Fonts and deferring the loading of the CSS. As such Autoptimize will allow you to improve your performance (load time measured in seconds) and will probably also help you tackle some specific Pagespeed warnings. If you want to improve further, you will probably also have to look into e.g. page caching and your webserver configuration, which will improve real performance (again, load time as measured by e.g. https://webpagetest.org) and your “performance best practice” pagespeed ratings.

¿Qué puedo hacer con la API?

A whole lot; there are filters you can use to conditionally disable Autoptimize per request, to change the CSS- and JS-excludes, to change the limit for CSS background-images to be inlined in the CSS, to define what JS-files are moved behind the aggregated one, to change the defer-attribute on the aggregated JS script-tag, … There are examples for some filters in autoptimize_helper.php_example and in this FAQ.

¿Cómo funciona una CDN?

Starting from version 1.7.0, CDN is activated upon entering the CDN blog root directory (e.g. http://cdn.example.net/wordpress/). If that URL is present, it will used for all Autoptimize-generated files (i.e. aggregated CSS and JS), including background-images in the CSS (when not using data-uri’s).

If you want your uploaded images to be on the CDN as well, you can change the upload_url_path in your WordPress configuration (/wp-admin/options.php) to the target CDN upload directory (e.g. http://cdn.example.net/wordpress/wp-content/uploads/). Do take into consideration this only works for images uploaded from that point onwards, not for images that already were uploaded. Thanks to BeautyPirate for the tip!

Why aren’t my fonts put on the CDN as well?

Autoptimize supports this, but it is not enabled by default because non-local fonts might require some extra configuration. But if you have your cross-origin request policy in order, you can tell Autoptimize to put your fonts on the CDN by hooking into the API, setting autoptimize_filter_css_fonts_cdn to true this way;

add_filter('autoptimize_filter_css_fonts_cdn',__return_true);

I’m using Cloudflare, what should I enter as CDN root directory

Nothing, when on Cloudflare your autoptimized CSS/ JS is on the Cloudflare’s CDN automatically.

¿Cómo puedo forzar que los archivos unificados sean CSS o JS estático en lugar de PHP?

If your webserver is properly configured to handle compression (gzip or deflate) and cache expiry (expires and cache-control with sufficient cacheability), you don’t need Autoptimize to handle that for you. In that case you can check the “Save aggregated script/css as static files?”-option, which will force Autoptimize to save the aggregated files as .css and .js-files (meaning no PHP is needed to serve these files). This setting is default as of Autoptimize 1.8.

¿Cómo funciona «excluir de la optimización»?

Both CSS and JS optimization can skip code from being aggregated and minimized by adding “identifiers” to the comma-separated exclusion list. The exact identifier string to use can be determined this way:

  • if you want to exclude a specific file, e.g. wp-content/plugins/funkyplugin/css/style.css, you could simply exclude “funkyplugin/css/style.css”
  • if you want to exclude all files of a specific plugin, e.g. wp-content/plugins/funkyplugin/js/*, you can exclude for example “funkyplugin/js/” or “plugins/funkyplugin”
  • if you want to exclude inline code, you’ll have to find a specific, unique string in that block of code and add that to the exclusion list. Example: to exclude <script>funky_data='Won\'t you take me to, Funky Town'</script>, the identifier is “funky_data”.

Configurar y diagnosticar problemas en Autoptimize

After having installed and activated the plugin, you’ll have access to an admin page where you can to enable HTML, CSS and JavaScript optimization. According to your liking, you can start of just enabling all of them, or if you’re more cautious one at a time.

If your blog doesn’t function normally after having turned on Autoptimize, here are some pointers to identify & solve such issues using “advanced settings”:

  • If all works but you notice your blog is slower, ensure you have a page caching plugin installed (WP Super Cache or similar) and check the info on cache size (the soution for that problem also impacts performance for uncached pages) in this FAQ as well.
  • In case your blog looks weird, i.e. when the layout gets messed up, there is problem with CSS optimization. Try excluding one or more CSS-files from being optimized. You can also force CSS not to be aggregated by wrapping it in noptimize-tags in your theme or widget or by adding filename (for external stylesheets) or string (for inline styles) to the exclude-list.
  • In case some functionality on your site stops working (a carroussel, a menu, the search input, …) you’re likely hitting JavaScript optimization trouble. Change the “Aggregate inline JS” and/ or “Force JavaScript in head?” settings and try again. Excluding ‘js/jquery/jquery.js’ from optimization (see below) and optionally activating “Add try/catch wrapping“) can also help. Alternatively -for the technically savvy- you can exclude specific scripts from being treated (moved and/ or aggregated) by Autoptimize by adding a string that will match the offending Javascript or excluding it from within your template files or widgets by wrapping the code between noptimize-tags. Identifying the offending JavaScript and choosing the correct exclusion-string can be trial and error, but in the majority of cases JavaScript optimization issues can be solved this way. When debugging JavaScript issues, your browsers error console is the most important tool to help you understand what is going on.
  • If your theme or plugin require jQuery, you can try either forcing all in head and/ or excluding jquery.js (and jQuery-plugins if needed).
  • If you can’t get either CSS or JS optimization working, you can off course always continue using the other two optimization-techniques.
  • If you tried the troubleshooting tips above and you still can’t get CSS and JS working at all, you can ask for support on the WordPress Autoptimize support forum. See below for a description of what information you should provide in your “trouble ticket”

¿He excluido los archivos, pero aun están siendo optimizados?

AO minifies excluded JS/ CSS if the filename indicates the file is not minified yet. As of AO 2.5 you can disable this on the “JS, CSS & HTML”-tab under misc. options by unticking “minify excluded files”.

Help, I have a blank page or an internal server error after enabling Autoptimize!!

Asegúrate que no estas ejecutando otros plugins de minimización de HTML, CSS o JS (BWP minify, WP minify, …) simultaneamente con Autoptimize o desactiva esa funcionalidad en tu plugin de caché de páginas (W3 Total Cache, WP Fastest Cache, …). Prueba a activar solamente la optimización de CSS o la de JS para ver cuál es la causa del error del servidor y sigue los pasos genéricos del diagnóstico para encontrar una solución.

But I still have blank autoptimized CSS or JS-files!

If you are running Apache, the .htaccess file written by Autoptimize can in some cases conflict with the AllowOverrides settings of your Apache configuration (as is the case with the default configuration of some Ubuntu installations), which results in “internal server errors” on the autoptimize CSS- and JS-files. This can be solved by setting AllowOverrides to All.

Can’t log in on domain mapped multisites

Domain mapped multisites require Autoptimize to be initialized at a different WordPress action, add this line of code to your wp-config.php to make it so to hook into setup_theme for example:

define( 'AUTOPTIMIZE_SETUP_INITHOOK', 'setup_theme' );

I get no error, but my pages are not optimized at all?

Autoptimize does a number of checks before actually optimizing. When one of the following is true, your pages won’t be optimized:

  • when in the customizer
  • if there is no opening <html tag
  • if there is <xsl:stylesheet in the response (indicating the output is not HTML but XML)
  • if there is <html amp in the response (as AMP-pages are optimized already)
  • if the output is an RSS-feed (is_feed() function)
  • if the output is a WordPress administration page (is_admin() function)
  • if the page is requested with ?ao_noptimize=1 appended to the URL
  • if code hooks into Autoptimize to disable optimization (see topic on Visual Composer)
  • if other plugins use the output buffer in an incompatible manner (disable other plugins selectively to identify the culprit)

Visual Composer, Beaver Builder and similar page builder solutions are broken!!

Disable the option to have Autoptimize active for logged on users and go crazy dragging and dropping 😉

Help, my shop checkout/ payment don’t work!!

Disable the option to optimize cart/ checkout pages (works for WooCommerce, Easy Digital Downloads and WP eCommerce).

¡Revolution Slider está roto!

Make sure js/jquery/jquery.js is in the comma-separated list of JS optimization exclusions (this is excluded in the default configuration).

I’m getting “jQuery is not defined” errors

In that case you have un-aggregated JavaScript that requires jQuery to be loaded, so you’ll have to add js/jquery/jquery.js to the comma-separated list of JS optimization exclusions.

I use NextGen Galleries and a lot of JS is not aggregated/ minified?

NextGen Galleries does some nifty stuff to add JavaScript. In order for Autoptimize to be able to aggregate that, you can either disable Nextgen Gallery’s resourced manage with this code snippet add_filter( 'run_ngg_resource_manager', '__return_false' ); or you can tell Autoptimize to initialize earlier, by adding this to your wp-config.php: define("AUTOPTIMIZE_INIT_EARLIER","true");

¿Qué es noptimize?

Starting with version 1.6.6 Autoptimize excludes everything inside noptimize tags, e.g.:
<!--noptimize--><script>alert(‘this will not get autoptimized’);</script><!--/noptimize-->

You can do this in your page/ post content, in widgets and in your theme files (consider creating a child theme to avoid your work being overwritten by theme updates).

Can I change the directory & filename of cached autoptimize files?

Yes, if you want to serve files from e.g. /wp-content/resources/aggregated_12345.css instead of the default /wp-content/cache/autoptimize/autoptimize_12345.css, then add this to wp-config.php:

define('AUTOPTIMIZE_CACHE_CHILD_DIR','/resources/');
define('AUTOPTIMIZE_CACHEFILE_PREFIX','aggregated_');

Can the generated JS/ CSS be pre-gzipped?

Yes, but this is off by default. You can enable this by passing ´true´ to ´autoptimize_filter_cache_create_static_gzip´. You’ll obviously still have to configure your webserver to use these files instead of the non-gzipped ones to avoid the overhead of on-the-fly compression.

¿Qué hace «Eliminar los emojis»?

This new option in Autoptimize 2.3 removes the inline CSS, inline JS and linked JS-file added by WordPress core. As such is can have a small positive impact on your site’s performance.

¿Es útil «quitar las cadenas de consulta»?

Although some online performance assessment tools will single out “query strings for static files” as an issue for performance, in general the impact of these is almost non-existant. As such Autoptimize, since version 2.3, allows you to have the query string (or more precisely the “ver”-parameter) removed, but ticking “remove query strings from static resources” will have little or no impact of on your site’s performance as measured in (milli-)seconds.

¿(Cómo) debería optimizar las Google Fonts?

Las Google Fonts se cargan normalmente mediante un archivo CSS enlazado que bloquea la carga. Si tienes un tema y plugins que utilizan Google Fonts, es posible que acabes con varios de estos archivos CSS. Autoptimize (desde la versión 2.3) ahora te permite reducir el impacto de las Google Fonts eliminándolas por completo u optimizando la forma en que se cargan. Hay dos tipos de optimización: la primera es «combinar y enlazar», que reemplaza todas las solicitudes de Google Fonts por una sola solicitud, que seguirá bloqueando la carga, pero permitirá que las fuentes se carguen inmediatamente (lo que significa que no verás que las fuentes cambien mientras se esté cargando la página). La alternativa es «combinar y cargar asíncronamente», lo que utiliza JavaScript para cargar las fuentes de una manera que no bloquee la carga, pero que podría causar un «flash de texto sin estilo».

¿Debería usar la «preconexión»?

Preconnect is a somewhat advanced feature to instruct browsers (if they support it) to make a connection to specific domains even if the connection is not immediately needed. This can be used e.g. to lessen the impact of 3rd party resources on HTTPS (as DNS-request, TCP-connection and SSL/TLS negotiation are executed early). Use with care, as preconnecting to too many domains can be counter-productive.

When can(‘t) I async JS?

JavaScript files that are not autoptimized (because they were excluded or because they are hosted elsewhere) are typically render-blocking. By adding them in the comma-separated “async JS” field, Autoptimize will add the async flag causing the browser to load those files asynchronously (i.e. non-render blocking). This can however break your site (page), e.g. if you async “js/jquery/jquery.js” you will very likely get “jQuery is not defined”-errors. Use with care.

¿Cómo funciona la optimización de imágenes?

Cuando la optimización de imágenes está activada, Autoptimize buscará archivos png, gif, jpeg (.jpg) en las etiquetas de las imágenes y en los archivos CSS que se cargan desde tu propio dominio y cambiará el «src» (origen) al ShortPixel CDN para ellas. Importante: esto solo puede funcionar para imágenes disponibles públicamente, de lo contrario, el proxy de optimización de imágenes no podrá obtener la imagen para optimizarla, por lo que, los corta fuegos, proxies, la protección por contraseña o, incluso, la prevención de enlazado, podrían romper la optimización de las imágenes.

¿Puedo usar la optimización de imágenes para mi intranet/sitio protegido?

No, la optimización de la imagen depende de la capacidad del servicio externo de optimización de imágenes para obtener la imagen original de tu sitio, optimizarla y guardarla en el CDN. Si tus imágenes no pueden ser descargadas por visitantes anónimos (debido a un cortafuegos/proxy/protección por contraseña/protección de enlazado), la optimización de las imágenes no funcionará.

¿Dónde puedo saber más sobre optimización de imágenes?

Echa un vistazo a la FAQ de ShortPixel.

¿Puedo desactivar la escucha de Autoptimize sobre las purgas de la caché de páginas?

As from AO 2.4 AO “listens” to page cache purges to clear its own cache. You can disable this behavior with this filter;

add_filter('autoptimize_filter_main_hookpagecachepurge','__return_false');

Algunos de los caracteres no ASCII se pierden después de la optimización

By default AO uses non multibyte-safe string methods, but if your PHP has the mbstring extension you can enable multibyte-safe string functions with this filter;

add_filter('autoptimize_filter_main_use_mbstring', '__return_true');

I can’t get Critical CSS working

Check the FAQ on the (legacy) “power-up” here, this info will be integrated in this FAQ at a later date.

Do I still need the Critical CSS power-up when I have Autoptimize 2.7?

When both Autoptimize 2.7 and the separate Critical CSS power-up are installed and active, the power-up will handle the critical CSS part. When you disable the power-up, the integrated critical CSS code in Autoptimize 2.7 will take over.

What does “enable 404 fallbacks” do? Why would I need this?

Autoptimize caches aggregated & optimized CSS/ JS and links to those cached files are stored in the HTML, which will be stored in a page cache (which can be a plugin, can be at host level, can be at 3rd party, in the Google cache, in a browser). If there is HTML in a page cache that links to Autoptimized CSS/ JS that has been removed in the mean time (when the cache was cleared) then the page from cache will not look/ work as expected as the CSS or JS were not found (a 404 error).

This setting aims to prevent things from breaking by serving “fallback” CSS or JS. The fallback-files are copies of the first Autoptimized CSS & JS files created after the cache was emptied and as such will based on the homepage. This means that the CSS/ JS migth not apply 100% on other pages, but at least the impact of missing CSS/ JS will be lessened (often significantly).

When the option is enabled, Autoptimize adds an ErrorDocument 404 to the .htaccess (as used by Apache) and will also hook into WordPress core template_redirect to capture 404’s handled by WordPress. When using NGINX something like below should work (I’m not an NGINX specialist, but it does work for me);

location ~* /wp-content/cache/autoptimize/.*\.(js|css)$ {
    try_files $uri $uri/ /wp-content/autoptimize_404_handler.php;
}

What open source software/ projects are used in Autoptimize?

The following great open source projects are used in Autoptimize in some form or another:

Where can I get help?

You can get help on the wordpress.org support forum. If you are 100% sure this your problem cannot be solved using Autoptimize configuration and that you in fact discovered a bug in the code, you can create an issue on GitHub. If you’re looking for premium support, check out our Autoptimize Pro Support and Web Performance Optimization services.

No quiero seguir usándolo, ¿cómo debería eliminar Autoptimize?

  • Desactivar el plugin (esto eliminará las opciones y la caché)
  • Eliminar el plugin
  • Clear any cache that might still have pages which reference Autoptimized CSS/JS (e.g. of a page caching plugin such as WP Super Cache)

¿Cómo puedo ayudar/ contribuir?

Just fork Autoptimize on Github and code away!

Reseñas

20 de septiembre, 2020
If you think your work is done installing WP Fastest Cache turning a few things on and being done with it you would be wrong. While WPFC will improve your score in a couple of ways, Autoptimize will work with it to make it even better. Adding Critical CSS will be the icing on the cake. The cherry on top, however, was a lovely exchange via email I had with Frank, one of the plugin developers who was kind enough to gently guide me from an average Google Page Speed Insights score of 50 to an average score of 84. 3 out of 10 times, I'm even in the green with a score of 90-92. I have been working all week to improve my site performance and I couldn't have done it without Autoptimize. For those interested, my setup ended being this: Autoptimize WP Fastest Cache reSmush.it Image Optimization WebP Express (further image optimization for modern browsers) Asset Cleanup (to remove WooCommerce assets from non-shop pages)
19 de septiembre, 2020
After installing this plugin it helped with performance grade on website testing engines. It uplifted the performance grade from D to B. But extremely slowed down my website. Decreased the loading time and I had to uninstall the plugin. Instead I used the WP-Optimize – Clean, Compress, Cache - plugin and it's just amazing. Try that one and you will be more satisfied.
17 de septiembre, 2020
I installed the plugin and default setting worked but I could not enable "lazy load" because of my METASLIDER plugin. The autor replied fast and we found a way to fix it. This support is OUTSTANDING - thank you Frank!
17 de septiembre, 2020
Works as expected, uses core functionality where possible and doesn't have any excessive or annoying ads. I don't personally use it because of how my servers are setup, but I do recommend it to all my Total theme customers. - AJ
14 de septiembre, 2020
After several weeks of trying to figure out why I (and my web host support) kept getting blocked from getting in via my wp-admin page (page 404s i believe?). I tried activating and deactivating various plugins (I have about 30). I opened several support tickets with my host's customer support. Finally Tier 2 support (higher level) identified this as the culprit and things now work fine. Apparently AO does not work with their technology. They suggested other caching plugins. I am sure AO is useful otherwise. Definitely back up before activating a plugin and make sure you have a good web host support. Again, if wp-admin access is your problem, it might be this plugin based on your host's technical setup.
9 de septiembre, 2020
hello, I had to uninstall the plugin because the internal google ads engine was revealing the autooptimize cache folder as malicious software. Please check surely it is a false positive but it has to be solved.
Leer la 1.137 reseñas

Colaboradores y desarrolladores

«Autoptimize» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«Autoptimize» ha sido traducidos a 28 idioma local. Gracias a los traductores por sus contribuciones.

Traduce «Autoptimize» 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

2.7.7

  • critical CSS: make sure pages get a path-based rule even if a CPT or template matches (when “path based rules for pages” option is on)
  • critical CSS: make sure the “unload CCSS javascript” is only added once
  • settings screens: switch jQuery .attr() to .prop() as suggested by jQuery Migrate to prepare for the great oncoming big jQuery updates
  • HTML minify: reverse placeholder array to make sure last replaced placeholder is changed back first to fix rare issues
  • security fix: kudos to Erin Germ for finding & reporting an authenticated XSS vulnerability
  • security fix: props to an anonymous pentester for finding & reporting an authenticated malicous file upload vulnerability

2.7.6

  • fix for top frontend admin-bar being invisible when “inline & defer” is active.
  • fix for 3rd party CSS-files not being deferred when “inline & defer” is active.
  • small copy changes on Extra settings screen.

2.7.5

  • urgent fix for Google Fonts aggregate & preload that broke badly in 2.7.4.

2.7.4

  • Image optimization: also optimize icon links
  • Image optimization: fix webp-detection for Safari (contributed by @pinkasey)
  • Image lazyload: remove CSS that hides the placeholder image/ sets transistion between placeholder and final image
  • Critical CSS: new advanced option to unload CCSS on onLoad
  • Critical CSS improvement: cache templates in a transient to avoid overhead of having to search filesystem time and time again (contributed by @pratham2003)
  • Critical CSS improvement: better but still experimental jQuery deferring logic
  • Critical CSS fix: prevent MANUAL template-based rules being overwritten
  • CSS Inline & defer: move away from old loadCSS-based approach to Filamentgroup’s new, simpler method
  • 404 fallback enabled by default for new installations
  • changed all occurences of blacklist/ whitelist to blocklist/ allowlist. The filters autoptimize_filter_js_whitelist and autoptimize_filter_css_whitelist still work in 2.7.4 but usage is deprecated and should be replaced with autoptimize_filter_js_allowlist and autoptimize_filter_css_allowlist.
  • updated readme to explicitly confirm this is GPL + praise open source projects used in Autoptimize as praise was long overdue!
  • tested and confirmed working on WordPress 5.5 beta 2

2.7.3

  • Critical CSS: cache settings in the PHP process instead of re-fetching them
  • Critical CSS: shorter intervals between calls to criticalcss.com (shortening the asynchronous job queue processing time)
  • inline & defer CSS: fix for some excluded files not being preloaded
  • 404 fallback: only create fallback files for CSS/ JS, not for (background-)images
  • copy changes as suggested by Cyrille (@css31), un grand merci!
  • misc. other minor fixes, see the GitHub commit log.

2.7.2

  • Critical CSS: fix settings page issues with certain translation strings
  • Critical CSS: fix “inline & defer” not being “seen” on multisite network settings
  • Critical CSS: add links on path-based rules
  • Critical CSS: fix for non-asci URL’s not matching rules
  • Improvement: auto-disable autoptimize on misc. page builder URL’s
  • Improvement: don’t change non-aggregated CSS if it already has an onload attribute
  • Image lazyload improvement: remove &quot; from around background images

2.7.1

2.7.0

  • Integration of critical CSS power-up.
  • New option to ensure missing autoptimized files are served with fallback JS/ CSS.
  • Batch of misc. smaller improvements & fixes, more info in the GitHub commit log.

2.6.2

  • auto-exclude images from lazyload when they have loading="eager" attribute.
  • bugfix: don’t take querystring into account when deciding as-value for preloaded resources.
  • bugfix; ensure lqip images (used when both image optimization and lazyload are active) always work by normalizing the URL before sending it to shortpixel.
  • minimum WordPress version bumped to 4.4.

2.6.1

  • bugfixes for multiple lazyload bugs causing images not to load or load incorrectly
  • bugfixes for multiple multisite bugs causing settings-screen to be unavailable
  • bugfix re-added 3rd parameter to autoptimize_filter_js_minify_excluded-filter to ensure backwards-compatibility and thus avoid breaking Smart Cookie Kit which expected that 3rd parameter.

2.6.0

  • New: Autoptimize can be configured at network level or at individual site-level when on multisite.
  • Extra: new option to specify what resources need to be preloaded.
  • Extra: add display=swap to Autoptimized (CSS-based) Google Fonts.
  • Images: support for lazyloading of background-images when set in the inline style attribute of a div.
  • Images: updated to lazysizes 5.2.
  • CSS/ JS: no longer add type attributes to Autoptimized resources.
  • Improvement: cache clearing now also integrates with Kinsta, WP-Optimize & Nginx helper.
  • Added “Critical CSS” tab to highlight the criticalcss.com integration, which will be fully included in Autoptimize 2.7.
  • Batch of misc. smaller improvements & fixes, more info in the GitHub commit log.

2.5.1

  • Imágenes: Optimización y carga diferida también para <picture><source>
  • Imágenes: Mejoras misceláneas en la carga diferida
  • Imágenes: Actualizado a LazySizes 5.0.0
  • CSS: Mejoras en la lógica de aplazamiento de los recursos CSS no unificados.
  • Página de ajustes: Mostrar opciones avanzadas de «JS, CSS y HTML» por defecto (muchas personas no veían el botón)

2.5.0

  • moved image optimization to a separate tab and move all code to a separate file.
  • added lazyloading (using lazysizes)
  • added webp support (requires image optimization and lazyloading to be active)
  • added option to enable/ disable the minification of excluded JS/ CSS files (on by default)
  • misc. bugfixes and smaller improvements

older