Chapter 11. Tweaking ASP.NET Web Forms performance

 

This chapter covers

  • Improving HTML
  • Changing your settings
  • Utilizing a code profiler

In the previous chapter, we started looking deeper into the performance of an ASP.NET MVC application. In this chapter, we begin to look at specific techniques for ASP.NET Web Forms performance. (Chapter 10 focused on ASP.NET MVC performance.)

As you’ve progressed through this book, you’ve cut the load time of the Surf Store application in half. That is pretty impressive, considering it was all done using front-end optimization techniques. But what happens when you’ve optimized the front end of your website as much as possible, yet your web pages still load slowly? This is a good indication that you should look at the code that powers the application. Although the performance of a website can be drastically improved by focusing on the front end, there will undoubtedly come a time when a back-end code issue will affect your application.

In this chapter we’re going to look at ASP.NET Web Forms-specific techniques that will help improve your page load times as well as the overall performance of your application. Then we’ll look at a tool that will help you identify bottlenecks or inefficient code in your application. This profiling tool is different from the tools you’ve used so far, because it will integrate with the back-end code and pinpoint exact pieces of code that may be causing bottlenecks.

11.1. HTML improvements

11.2. Web.config settings

11.3. Response.Redirect vs. Server.Transfer

11.4. Utilizing a code profiler

11.5. Fixing the issue

11.6. Summary

sitemap