Shared hosting isn’t the ideal environment for speeding up WordPress with W3 Total Cache. There are features that just don’t work well on a shared server. In addition, if you run into server configuration issues there isn’t much you can do about it if your site is hosted on a shared server.
In an ideal WordPress world, every WordPress website would be hosted in a private environment. However, many WordPress websites don’t generate the kind of traffic or revenue needed to justify anything more than bare-bones shared hosting.
If that’s where you find yourself, it’s easy to get frustrated and give up on W3TC entirely. Instead of throwing in the towel, what you really need is a simple baseline configuration – a starting point that produces a measurable improvement in site performance. From that starting point you can customize W3TC for additional gains, but at least you’ll know right off-the-bat that you’re starting the process with a mark in the win column.
We will never take money to promote others, everything you read is genuine. Learn more.
This post is the final part of our four-part series on W3 Total Cache. If you want to read all of the W3TC goodness we have on tap, check out the rest of our Ultimate Guide to W3 Total Cache:
You might be surprised to learn that all it takes to produce a measurable improvement in site performance is page and browser caching. That’s good news because no other modules perform consistently from one shared hosting environment to the next.
What that means is that you only have to mess with three of W3TC’s sixteen menus to see a noteworthy boost in site performance: General Settings, Page Cache, and Browser Cache.
Ideally, you’ll come to this tutorial with a brand new, untouched W3TC installation. However, if that isn’t the case, the first thing to do is to clear the slate by resetting the default settings. To do that go to Performance > General Settings and scroll all the way to the bottom of the page. Select the very last button you see to Restore Default Settings.
Now we’re ready to get started.
First, enable the Page Cache and Browser Cache modules from the General Settings menu. To enable these modules, follow these steps:
Next, configure page caching. Go to the Page Cache menu and make sure the following settings are selected:
Finally, configure browser caching. From the Browser Cache menu just a couple of minor modifications are needed:
Lightweight and fast, Hummingbird caches, minifies, combines, defers and compresses, making optimizations in line with Google PageSpeed, and turning your website into a lean, mean, speed machine.
This plugin configuration was thoroughly tested.
A standardized test process was developed and used to test out W3TC configuration on each of the servers.
That’s a tough question to answer.
The improvement you will see after installing W3TC and configuring it exactly as we’ve recommended cannot be predicted. There are just too many factors in play. However, we can show you the results that these settings produced when we tested them out.
The test site is a pretty lightweight website. So it should load pretty fast without any caching, right? Yes, and Pingdom agrees.
In every case, the average load time was less than a second and a half — not too shabby and nothing to complain about. How much improvement can you really expect by implementing just page caching and browser caching on a site that already loads pretty fast? Not much, right?
With W3TC installed and configured, and the site homepage cached, our test site loaded significantly faster.
On average, the test site loaded 33% faster with page and browser caching enabled. Here are the numbers so you can judge the results for yourself:
Keep in mind that our test site started the process as a light site. Heavier sites can expect to see a larger improvement in site performance with the same settings in effect.
There is so much more that you can do with W3TC, even on a shared server. Minification has the greatest potential to boost website performance, but database and object caching may also prove helpful for some sites. If you’re using WordPress and W3TC on a shared server use these settings as a starting point, but not as the final plugin configuration. If you do, you’ll be leaving a lot of potential improvement on the table.
Your next step should be to take a look at the minify, database cache, and object cache modules in W3TC to determine if any improvement in site performance can be produced by configuring those modules. If you’re intimidated by that thought, refer to the second part of this Ultimate Guide to W3 Total Cache in which all of the plugin modules are explained.