Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First thing you should do is measure current state, there are many tools to help you in this task :</p> <ul> <li><a href="https://developers.google.com/pagespeed/" rel="nofollow noreferrer">Google page speed</a></li> <li><a href="http://yslow.org/" rel="nofollow noreferrer">YSlow</a></li> <li><a href="http://www.webpagetest.org/" rel="nofollow noreferrer">Web page test</a></li> <li><a href="http://tools.pingdom.com/fpt/" rel="nofollow noreferrer">Pingdom tools</a></li> <li><a href="http://fiddler2.com/fiddler2/" rel="nofollow noreferrer">Fiddler 2</a></li> <li><a href="https://addons.mozilla.org/en-US/firefox/addon/viewstate-size/" rel="nofollow noreferrer">ViewState Size</a> - Firefox ext.</li> <li><a href="https://addons.mozilla.org/en-US/firefox/addon/aspnet-viewstate-viewer/?src=api" rel="nofollow noreferrer">ViewState viewer</a> - Firefox ext.</li> </ul> <p>things that you need to measure</p> <ul> <li>what is the time to first byte, or time needed for server to generate page, it should be below 0.5 seconds. If this time is greater that this use Visual Studio profiler to locate bottlenecks and optimize critical parts</li> <li>Measure viewstate size and analyze contents, since you are using lots of gridviews, this is possibly the problem, here on SO there are dozens of <a href="https://stackoverflow.com/questions/1102385/asp-net-gridviews-viewstates">posts</a> related to that problem</li> <li><strong>UNDERSTAND</strong> ViewState, and how it's working, excellent post <a href="http://weblogs.asp.net/infinitiesloop/archive/2006/08/03/Truly-Understanding-Viewstate.aspx" rel="nofollow noreferrer">here</a></li> <li>you should decrease number of requests, combine css and JavaScript in one file, there are plenty of <a href="https://www.google.com/#hl=en&amp;output=search&amp;sclient=psy-ab&amp;q=combine+and+minify+&amp;oq=combine+and+minify+&amp;aq=f&amp;aqi=g3&amp;aql=&amp;gs_nf=1&amp;gs_l=hp.3..0l3.252.3002.0.3714.19.15.0.4.4.0.153.1751.4j11.19.0.aKxBz-wcA-I&amp;pbx=1&amp;bav=on.2,or.r_gc.r_pw.r_cp.r_qf.,cf.osb&amp;fp=8c7646f229469991&amp;biw=1390&amp;bih=909" rel="nofollow noreferrer">free tools to do that</a></li> <li>Turn on IIS gzip compression</li> <li>Use fiddler to see how are your requests cached locally</li> <li>Use <a href="http://www.w3schools.com/css/css_image_sprites.asp" rel="nofollow noreferrer">Css Image Sprites</a> for small images</li> <li>Use asp.net caching, it's really good and it offers solutions for many usage scenarios, especially helpful in situations where increased traffic is the problem</li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload