Cómo resolver el “inline small css” y “minify css” de GTMetrix.com

Este tema me dió bastante guerra. Por más que configuraba de forma manual o automática mi W3 Total Cache no había forma de que desapareciese. Después me di cuenta de que utilizo también CloudFlare y que lo tengo activado como Extension en W3 Total Cache.

El tema es que lo tenía activo en ambos y no había forma de que funcionase y GTMetrix eliminase este punto flojo en sus análisis.

La solución es desactivar por completo el Minimize en W3 Total Cache, porque no necesitamos hacerlo en nuestro servidor ya que puede hacerlo directamente CloudFlare. Para desactivar el Minimize en local debemos hacerlo en 2 lugares distintos:

  • En los General settings de W3 Total Cache
  • En cada uno de los 3 puntos del apartado específico de Minimize de W3 Total Cache


NOTE:- If you are using the minify settings of the CloudFlare then don’t use the minify settings of the W3 Total Cache plugin. De esta forma descargas un poco de trabajo al plugin y evitas conflictos.

Is using W3 Total cache With CloudFlare Safe?

You don’t need to worry about anything. Just make sure that you don’t use the minify settings of both the platforms. Use only cloudFlare minify settings to minify CSS, HTML, and Javascript files.

Never use the minify settings of the plugin with the CloudFlare. You will see the effective results with the speed of your website. The combination of CloudFlare and W3 Total Cache plugin works every time. If you still face any difficulty then feel free to ask.


Otra fuente que también confirma esto:

Combine External CSS in WordPress

Combine external CSS files in WordPress with W3 total cache plugin. If you are using cloudflare, this job can be easily done by setting up Rocket Loader active.


Aquí puedes encontrar todos los detalles de estas 2 referencias:



A Quick Check To Be Sure

If your travel blog happens to be running Cloudflare (which has a free version of their service by the way) be sure to log into your account, go to Performance Settings, and check your ‘Auto-Minify’ settings. If they’re enabled, be sure you’re not using another minify plugin at the same time. Also, sites running W3 Total Cache (my preferred caching plugin) should check under ‘General Settings’ that minfying isn’t enabled there either.

Provided you’re not using more than one minify service at the same time, it’s an effective and recommended way to reduce your blog’s loading time.


2.1.3 Minify

We have tested using Minification in W3TC extensively, and find that leaving all the minification to Cloudflare works much better.  Cloudflare, intelligently minifies and combines javascript, as well as re-ordering its loading to ensure an optimized page load time (via its Rocket Loader).  Also, it does not combine CSS which is a common issue with site display problems and only minifies it.  There is absolutely no need to duplicate the minification here.


1.3. Minify

➥ Minify: Disabled

Minify is to reduce the number of javascript and css files by combining. It will weed out unnecessary codes from js, css and html as well. So it looks really important, doesn’t it?. But why didn’t we enable it?

Actually cloudflare also supports minify. It seems like cloudflare minify can give better performance. We noticed sometimes w3 total cache minify can break a site. But we didn’t encounter any single problem with cloudflare. So we enabled minify on cloudflare and disabled it on w3 total cache.

Please be noted that allowing minify both on w3 total cache and cloudflare can also break your site. So stay safe, use it at one place. We preferred cloudflare.



Aunque siempre hay alguno que lleva la contraria: https://www.webhostinghero.com/cloudflares-rocket-loader-with-w3-total-cache/