Removing the form runat=server tag from the Master Page is one of the ways to optimize Internet-facing websites built on the SharePoint 2010 platform. Unfortunately it also means losing some functionality such as Web Parts in content. Find out how to combine minimal Master Page markup with Web Parts in content.
Prefetching content allows users to access it more quickly what improves the user experience. Find out how to prefetch SharePoint search results and cut down your users’ waiting time.
Caching files using BLOB cache is a great performance improvement in SharePoint 2010 Web Content Management solutions. Unfortunately it turns out, that if your files are dynamically created, they are not being cached by BLOB cache. So is creating a custom caching solution the only option to have a good performing solution?
It is a common best practice, while working with the SharePoint server API, to always use context objects whenever possible. Because they have been already instantiated by SharePoint itself, reusing context data doesn’t cause additional calls to the database and allows you to create good performing solutions. However, just because you use SPContext.Current in your code, doesn’t mean your solution is built properly.
SharePoint 2010 contains Developer Dashboard which can be invaluable in optimizing custom solutions for performance. By default the Developer Dashboard is visible only to authenticated users, but sometimes you might want to show it to anonymous users as well. Sounds insane? Find out why you would want it and how to do it.