How to improve performance of a website

visit here for more...

How to Improve ASP.NET Performance[^]

or

tips-to-improve-the-performance-in-Asp-Net-application/[^]

1) Use Stored Procedures where ever possible...
2) Check your queries in the SPs. Remove unwanted fields from the queries...
3) Index the Tables which are used most in Select queries..
4) If you are using SQL Server as DB, monitor the queries to identify which queries take more time to execute.
5) Do not store large data in Sessions/Viewstate.

The above points are basic points.

http://www.infoworld.com/d/data-management/7-performance-tips-faster-sql-queries-262?page=0,0[^]

and Refer the above link

Hope this gives the start you need...

It seems lot of client side scripting, there are some non-normalized tables if you can refine them,
1. using client side scripting improves performance but if you use too much of it, it may increase data transportation time which in turn may effect the performance of page loading and post-back, decide between client side and server side code by taking the performance also into consideration, usually that's what lot of applications are doing these days.
2. If there are tables which don't have proper normalization try put normalization if missing
3. If handling huge data then use Stored Procedures, EDMS doesn't work very well with huge data manipulations yet.
4. If there are stored procedures remove selecting all columns instead use column names in select statements.
5. Put proper where clauses, select data as chunks put them either in temp tables or table variables if the table has millions of rows, don't try to put joins on the whole table itself
6. You can add indexes on the original table as well as on the temp tables as well, but see how indexes are working with performance on that table.
7. And remove unused variables and code from C# code and follow the guidelines for refactoring code in C#, there are many books/links available regarding it.
8. Make changes and see which one is very effective for your application, it depends.


When I was working with one State Govt client, table variables were crashing the stored procedures and temp tables were working very fine, against the rule of Microsoft. When I investigated, it is because they have lot of physical memory but very less RAM, as RAMs are more expensive and need little more work for installations they had been just adding up the physical memory.

So it always depends upon the situation there, and there are other good solutions that other people have given follow them too like removing unwanted state management and etc.