I cringed a little bit when I read this: "...none get enough traffic for me to have made caching or performance tuning a huge priority".<p>I don't mean to level criticism solely against the post author for this, because he is not alone, but I find this mentality inexcusable. This is especially true if you're using WordPress, for which there are a multitude of caching plug-ins. All of which will offer orders of magnitude better performance than allowing the blogging engine to build the page from scratch every time.<p>In other words, caching is <i>always</i> a priority. It's not an add-on or an after-thought, it should be part of your design.<p>Consider a scenario where someone asks you to add up three arbitrary numbers:<p>123 + 456 + 789<p>Now, imagine you type those in to a calculator to add them up. It takes you a few seconds. The output is 1368. You can easily remember this number, so the next time someone asks you what the result of 123 + 456 + 789 is, you can just say 1368. Not caching is like keying the numbers in to a calculator every time, rather than just relying on your memory.<p>I know this is a rudimentary example, and I know that most people running a WP blog probably know how caching works, but even if you don't "need" it today, why would you leave your blog set up so that it's constantly re-building content that can be cached by simply installing a WP plug-in?<p>I implore you. Make caching the second thing you do (after security) when setting up or building your web app.