Use Caching As Last Resort

Caching is not synonymous with performance. Your code should already be efficient. Caching should only be used as a last resort, after you’ve made all possible (and sensible) code optimizations.

Projects that use multiple levels of cache often demonstrate a misunderstanding of why caching is required in the first place.

50 Ways to Avoid Find and Fix ASP.NET Performance Issues