I had originally overlooked this KB article:http://www.sitefinity.com/support/knowledge-base/kb-article/b1154K-mkd-b1154T-cgb.aspx
Most of this stuff I had already done, however I had not disabled "Health Monitoring". Doing this seems to have helped my web site's performance.
As an aside, this past weekend I happened to be poking around my web site at around midnight. I noticed the public web pages were very zippy. CPU usage on my shared web server would, of course, be lower this late at night. This would certainly validate that some of the performance problems are merely due to me sharing the CPU with other hosted customers.
Also, don't forget your ASP.NET basics. Because I am now using a "CMS product", I was getting lazy about doing things that I consider essential in my own projects. Think about what you're requiring the CPU to do.
I went through and disabled lots of unneeded "Viewstate" in my master templates, as well as my Sitefinity pages. Make use of page caching, where possible. All the existing ASP.NET performance tips still apply.
I am now more happy than I was with the performance of my web site. It's still not great, but then again, it only cost me $10/month. I'm hoping 3.2 will help even more with performance.
I remain a bit perplexed about what portions of "Admin" web site are doing. Disabling "Health Monitoring" has certainly helped, but I can still easily produce 10+ second render times. This proves to be the case even while using "localhost". I can't impact much of this because it is part of the core Sitefinity product.