increase loading time

Lets say you have a regular html page that has text and 19 images that are .gif. how would you guys do this page in .net?

What exactly are you asking? How can you make the equivalent of this page in .NET? How to increase the loading time of the page using .NET? I'm not entirely sure what you're after..

well yes i am asking both

How can you make the equivalent of this page in .NET?
How to increase the loading time of the page using .NET?

.NET is a predominantly a server-side technology.  The HTML and images it presents to the client are downloaded the same way as HTML and images generated by any other technology (PHP, Cold Fusion, etc.)

I say "predominantly" because there are some canned javascript functions that are presented to the client which are .NET-specific.  Cold Fusion does the same thing.

The poster above is completely correct.  However if I am reading you right - you are looking for sort of a gallery solution?  There are some great freeware and payware solutions for this.  Check out -

http://www.asp.net/ControlGallery/default.aspx?Category=50&tabindex=2


Some of them are pretty advanced and offer the ability to automatically provide thumbnails of all the images - which can then further be clicked to see the "full" version.

Let me know if this is what you wanted.

If I'm understanding you correctly, you want to make the loading time longer for the page?

I was going under the assumption that was a typo.
It's much easier to make loading time longer - use bigger images, throw a few sleep() statements into the server-side code, serve images through an arbitrarily long chain of open redirects, etc.

crazychris_32 wrote:

If I'm understanding you correctly, you want to make the loading time longer for the page?

I don't want to make the loading time longer. I want to increase it mostly for vistors that maybe using phone line.

So you want the page to load normally for broadband users, and you want the page to take a longer time than usual for dial-up users... whats the point of this discrimination?

there must have been some mix up somewhere and someone didn't understand or something.


I want it to load the same for everyone no matter what kind of connection they have. For Broadband vistors it load faster anyway because they have more dl speed which we all know but i just want to know how can i make it better for the phone line visitors?

I was thinking maybe something with a database driven page or something.

That makes more sense. Lowering the compression on images, is one place to start. Reducing the number of images. Those are the big hitters. Obviously the same would apply to any flash items that you have on the page as those are rather bandwidth intensive for dialup users.

I can't see a database speeding up your website, it may be useful however for dynamic content.

I already have try that i also tried changing the format of some of the images. It help a little current loading time for 56k is 1 min. and 5 seconds.

I really think you should take a look at my solution above.  Since it generates thumbnail images the page is going to load much faster.

A database driven site wont help because the server still needs to send the html to the client. But you should make sure that the server supports compression.

Your options are pretty limited - the only real ways you can improve performance* are

• Reduce the amount of data you transfer. , Smaller HTML page, HTML Compression, smaller images with higher compression ratios.
• Better use of browser cache (less requests)
• Less images/css etc.. (again less requests)
• Bring your client 'closer' through Content Delivery Networks such as Akamai (lowers latency though generally an expensive option )

Edit: *assumes that server 'think-time' is more or less constant regardless of client type.

Server think-time is generally a very small percentage of the overall request time for dial-up users too e.g. 100ms thinktime + 60s transmission.

You could do prefetching.  This is somewhat controversial but it works.

There are two ways to do it.

Suppose you have a relatively standard setup like

index.html
   1_thumbnail.jpg -> 1.html
   2_thumbnail.jpg -> 2.html
   ...
   35_thumbnail.jpg -> 35.html

1.html
   1_large.jpg
   Next -> 2.html

2.html
   2_large.jpg
   Previous -> 1.html
   Next -> 3.html

...

The first way involves putting HTTP headers - or their <meta http-equiv="..." content="..."> equivalents - on each n.html to let the browser know that the "next" page in the sequence is (n + 1).html, and the "previous" page is (n - 1).html.  Some browsers are "smart" enough to begin loading page 17 will the user is gazing at image 16.

The second way is a little more heavy-handed.  On page 16, put javascript that acts as follows:

// wait until image 16 is fully loaded
// while the user is looking at image 16, start loading image 17
// if the user is still looking at image 16, start loading image 18

using new Image(...) constructors.  These will put the large images in the cache, so when the user clicks Next, the next page will be very quick to load.