Template fails to load in IE9 because of W3TC

Your friend is very likely correct; all you needed to do was to go to the “Performance” menu option (the one that W3TC installs) and go to the “Minify” sub-option. You can enable or disable it there, and select the level of “aggressivity” you wish to use Minify for.

In some hosts, checking “Rewrite URL structure” will fix the problem you’ve been having. In others, you might need to disable Minify completely. I have had similar CSS issues in the past, but the problem was almost always on the host configuration — I use several hosting providers. When I have full access (e.g. root account) on the host, I can obviously tailor it to suit W3TC best, of course, but on shared hosting accounts I’m limited to what the provider gives me, and so I have to tweak W3TC appropriately.

Please note that W3TC is not the culprit ?? It’s a fantastic plugin but ever so hard to configure properly. Unlike most WP plugins, which will work pretty much on all hosting providers out there, W3TC, due to the clever tricks it uses, has to work in tandem with the webserver software, and will try to make the best of what it can do — but sometimes needs human help to tweak settings. I can tell you that a server specifically tailored to work with W3TC can give your WordPress install such an increase of performance that it becomes uncanny (I’ve seen static sites that are slower to load!).

If your hosting provider has such an odd configuration that W3TC can help little to improve performance, you have two choices. The first is to use a different caching plugin (WP Super Cache remains still a good choice, and it’s easier to configure). The second, if you have full control over your DNS, is to use an external CDN — you can use CloudFlare, which is free, and fully integrated with W3TC. I have a few blogs on shared hosting (where performance depends so much on what the other users are doing…) with CloudFlare on top of everything — I get some 50-55% bandwidth savings that way, which is not bad for a free service. No, it doesn’t mean that your site will suddenly become twice as fast: it means that only half of the requests will go through to your shared hosting provider, and those requests will be superfast. Static images, CSS, JS, and embedded elements can thus be immediately served from CloudFlare and will never reach your WordPress installation. And W3TC will prepare that all for you automatically.

It’s worth giving it a try, but, of course, you will only see serious improvements on very busy websites.

Thanks for your reply Gwyneth! That will really help people with the same problem I had. I think W3TC is a bit beyond my expertise level at the time. I am not sure if I really need a performance boost or what benefits might repay the efforts of configuration. But at least now we know it’s not necessarily their fault…

I can tell you that one of my hosting providers, Dreamhost, has been rumoured to tell their clients not to use W3TC because tech support very likely had to deal with the trouble of fixing clients’ configuration all the time ?? And there is really not a one-size-fits-all configuration; the simplest defaults might not make a serious difference or even make your site slightly slower!

Otherwise (i.e. when patiently going through the configuration step by step, and test if it makes a difference), however, I truly appreciate its flexibility and features for all the extra tweaking that it allows ??

You might have noticed that W3TC has a “cache preview”. I found that amusing — why should one need to “preview” how the cache works? It should “simply work”, right? Well, no. The W3TC developers very correctly assumed that a few of their tweaks might not give the desired performance, and thus the need to add a “preview mode” to make sure that a particular set of settings is fine before deciding to go “live” on them. Very clever and useful of them.

Thanks for being so thorough Gwyneth.

Aww my pleasure; I’m glad someone found this information useful.

??