Nice work Bransin!
Can you comment on which areas you found Template Morsels to be most useful in improving performance? We’ve started experimenting with some performance tuning/caching options on some larger EE sites, but have had varying degrees of success.
Template Morsels helped in a few areas of the site. The addon is awesome if you’re finding yourself using many embeds to replicate certain sections with dynamic content and passing embed variables. I was actually recommended in using this by the awesome folks on EE help chat because I felt like I exhausted my energies in doing everything I could with total parse time and was unsatisfied.
The addon did amazing work by knocking off several seconds of total parse time for the large drop downs with the main site navigation. Since these drop downs belong to the header include, it was critical to make each embedded template parse quickly. I found the morsel refresh settings very useful and controlled unlike the native template caching in EE. I’ve always had issues in wanting to use the native EE cache templates on everything. The native EE template caching doesn’t work well with dynamic content and passing embed variables. You will often end up with strange duplicate content. Template morsels is a step further in caching that particular instance - a dynamic morsel/template. One feature that I would love to see baked into EE. Native EE template caching is only useful when working with very basic non-dynamic content.
When viewing any inside page the left navigation for each section used GWcode Categories by Leon Dijk. The parse time was around 6-7 seconds because of the many categories and hierarchy. The plugin Switchee also helped a great deal with GWcode Categories. Any morsel created with Template Morsels that involves a plugin works perfectly. I shaved off another 5-6 seconds.
I wanted to use this plugin more than often. One thing that should be very clear with this addon is that you cannot create a morsel for faster load time if it contains PHP.