So I’m at the stage in web programming where I’m past the “Look, Ma, I can put data in a grid and it shows up on the page.” I’m now at the, wow, this site is not as snappy as I want it to be. So, I enabled the “Net” tab in Firebug, closed my eyes, crossed my fingers, and went spelunking.
The first thing I noticed is that all of my .aspx pages are being “GET”ed at least three times. Is this normal? If not, what is “normal”? What affects the “GET”ing of the .aspx pages? I’m assuming that includes the time it takes to hit the database and render all the controls on the page. Is that true?
Perhaps what would really benefit me is a place I can look to get some “best practices” for these kinds of speed related issues.
Things to consider:
- Using IIS 6.0 via HTTPS
- We’re using Masterpages
-
We’re using Telerik controls
- A RadMenu
- A RadScriptManager
-
I’m certainly more of a thick client guy than a web guy
EDIT
Answers to questions below:
- The response code is 200
EDIT
Screen shot added:
FirebugScreenshot http://img187.imageshack.us/img187/5873/firebughelp.jpg
EDIT Added Additional Screenshot to include Request Headers
EDIT
Added links
EDIT: Here is the source of your two extra page loads:
As you can see in the rendered version the src attribute is empty, causing it to load the page two extra times.
You can probably fix this by using the runat server tag and having it resolve the urls automatically.
(or change <%# %> to <%= %> — since you need to have the version that outputs a string instead of the binding syntax).
Original answer removed since it was not related to the actual problem.