NETCore + AdminLTE (edit)

Install-Package Dynamic.NET.AdminLTE.ProjectTemplates (HAY HAY HAY) (HAY HAY HAY)

Jonathan Danylko

Full-Stack Web Architect w/ 25 years of exp. in Microsoft Technologies (HAY HAY HAY)

1. Application Caching
2. Optimize Your Images
3. Use Sprites
4. ETags
5. Bundle/Minify JavaScript/CSS
6. Compression/Zip
7. Minified HTML
8. Use AJAX When You Can
9. Minimize Database Calls
10. Use third-party services where they make sense

  1. Dotnet Memory Profiler
  2. Fiddler
  3. FireBug
  4. Google Page Speed Test
  5. Web Page Test (HAY HAY HAY) (HAY HAY HAY)

ASP.NET MVC 5 + AdminLTE + jQuery DataTables (HAY HAY HAY) (HAY HAY HAY) (HAY HAY HAY) - The collection of CRUD helpers for Dapper


ASP.NET Core MVC + AdminLTE + jQuery DataTables (HAY HAY HAY) (HAY HAY HAY) (HAY HAY HAY)

Setup AdminLTE Template in an Empty ASP.NET Core MVC Project

How to use AdminLTE 2 in an existing ASP.NET Core Project (HAY HAY HAY) (HAY HAY HAY) (HTML+CSS+JS)

HTML + CSS + JS + Bootstrap CRUD (HAY) (GOOD)

Tập trung 5 điểm sau:

A. Use the Application Initialization plugin

B. Use Auto-Start with .NET 4

C. Disable the idle-timeout (under IIS Reset)

D. Precompile the site

E. Fixing slow initial load for IIS

How do you improve your ASP.NET MVC application performance? (Glimpse - Performance Profiler) (Glimpse - Performance Profiler)


Steve Souders - High Performance Web Sites

A compiled list of possible sources of improvement are below:


  • Make use of a profiler to discover memory leaks and performance problems in your application. personally I suggest dotTrace
  • Run your site in Release mode, not Debug mode, when in production, and also during performance profiling. Release mode is much faster. Debug mode can hide performance problems in your own code.


  • Use CompiledQuery.Compile() recursively avoiding recompilation of your query expressions
  • Cache not-prone-to-change content using OutputCacheAttribute to save unnecessary and action executions
  • Use cookies for frequently accessed non sensitive information
  • Utilize ETags and expiration - Write your custom ActionResult methods if necessary
  • Consider using the RouteName to organize your routes and then use it to generate your links, and try not to use the expression tree based ActionLink method.
  • Consider implementing a route resolution caching strategy
  • Put repetitive code inside your PartialViews, avoid render it xxxx times: if you end up calling the same partial 300 times in the same view, probably there is something wrong with that. Explanation And Benchmarks



  • Use Forms Authentication, Keep your frequently accessed sensitive data in the authentication ticket


Load balancing

  • Utilize reverse proxies, to spread the client load across your app instance. (Stack Overflow uses HAProxy (MSDN).

  • Use Asynchronous Controllers to implement actions that depend on external resources processing.

Client side

  • Optimize your client side, use a tool like YSlow for suggestions to improve performance
  • Use AJAX to update components of your UI, avoid a whole page update when possible.
  • Consider implement a pub-sub architecture -i.e. Comet- for content delivery against reload based in timeouts.
  • Move charting and graph generation logic to the client side if possible. Graph generation is a expensive activity. Deferring to the client side your server from an unnecessary burden, and allows you to work with graphs locally without make a new request (i.e. Flex charting, jqbargraph, MoreJqueryCharts).
  • Use CDN's for scripts and media content to improve loading on the client side (i.e. Google CDN)
  • Minify -Compile- your JavaScript in order to improve your script size
  • Keep cookie size small, since cookies are sent to the server on every request.
  • Consider using DNS and Link Prefetching when possible.

Global configuration

  • If you use Razor, add the following code in your global.asax.cs, by default, Asp.Net MVC renders with an aspx engine and a razor engine. This only uses the RazorViewEngine.

    ViewEngines.Engines.Clear(); ViewEngines.Engines.Add(new RazorViewEngine());

  • Add gzip (HTTP compression) and static cache (images, css, ...) in your web.config <system.webServer> <urlCompression doDynamicCompression="true" doStaticCompression="true" dynamicCompressionBeforeCache="true"/> </system.webServer>

  • Remove unused HTTP Modules
  • Flush your HTML as soon as it is generated (in your web.config) and disable viewstate if you are not using it <pages buffer="true" enableViewState="false">