VB.NET page loads SLOW depending on computer requesting it

W

wizard04frms

I have an ASP.NET page on a remote server that takes about 60 seconds
to load from my Windows XP Pro SP2 computer with IE 6.0, but my local
copy opens instantly.

If I load the page from my Win2000 SP4 computer with IE 5.5, it loads
instantly as well.

Controls on the page are populated from an Access database.

I have tested the page by putting response.write(Now() & "<br>") in
various places (i.e., at the beginning and end of the document and at
the beginning and end of Page_Load), but these all end up within a
second of each other. So, I would assume that it has something to do
with the connection to the server based on either the Windows version
or IE version I'm using, but I'm not sure how to proceed from here.

Any help would be appreciated!
 
B

Bruce Barker

check the size of viewstate (if you have a grid on the page, this is a
commaon problem). to check with IE, save page to disk and check file size,
with firefox view page info.

-- bruce (sqlwork.com)
 
W

wizard04frms

Thanks for the response, Bruce.

I saved it with IE and the file size is 3.18KB. The main part of the
page is a DataGrid, as you mentioned.
 
W

wizard04frms

I've turned on tracing and found that the page takes less than 0.2
seconds to process.

Also, I can click the refresh button or enter the address in the
address bar of a new window and it loads instantly! But if I go back
and click on the link to it, I have to wait for it again. Could it be
a problem with the link on the previous page?
 
B

Bruce Barker

if the previous page uses a postback and Server.Redirect() then it can be.

-- bruce (sqlwork.com)
 
W

wizard04frms

It uses a Response.Redirect(). I've tried Server.Redirect(), and that
loads the page instantly! But for some reason, the browser continues
saying it's "Opening..." for 60 seconds after that - no problem, just
weird. Also, the address stays the same (the first page) in the
browser's address bar; is there a way to fix that?
 
W

wizard04frms

I figured it out! I have to use Response.Flush(), though I don't
really understand why.

Response.Redirect("page2.aspx", false)
Response.Flush()
Response.End()

Thanks for your help!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,743
Messages
2,569,478
Members
44,899
Latest member
RodneyMcAu

Latest Threads

Top