Performance should be in the mind of every Drupal developer and site builder as they are building a site. But let's be honest, while getting everything to just plain work and look good, speed doesn't always get to hold that #1 spot in your mind. Freeing up brain energy from potential performance issues is not necessarily a bad thing. Predicting which issues will have the biggest impact once a site launches is a task best left to wizards and sages. The best way to analyze and then tackle a site's performance issues is with data from the live production site. There are plenty of tools to help simulate that data, but nothing replaces good hard production data. Luckily Views Cache Bully has come to the rescue of distracted developers everywhere. Set it, forget it, and rest easy knowing that you now have one less reason for why your site might be crawling.
Why views caching?
Most the views on your site display the exact same information over and over, they just display it to different users. I know, I know, you are a prolific blog writer, but do you really publish a new post every 5 minutes? If you are feeling conservative, set the defaults to a short value and keep bumping them up as you come to realize how little these things change. Even if you only serve the cached results to five users that means five less trips through PHP and the database for those visitors.