They're being cached here okay. Though looks like several
of them are dynamic images referencing aspx files. The browser
can't cache these normally. It goes by URL, so it's going to call aspx
files each time and run them to get another stream.
Is your client computer date set right?
Another reason it may be slower is that you have too many
object references. Even when they load of the cache the
browser still needs to make a connection for each and
determine whether it needs to use the cache or re-load.
This can be expensive, especialy if the site is served from
a very distant location, nothing to do with ASP.NET here.
Looks like this is hosted somehwere in SoCal, so if it's being
used by someone in Europe it's going to be slow. For that
you need to reduce the number of object references to get
it rendered there faster.
"Stephane" <St******@discussions.microsoft.com> wrote in message
news:D0**********************************@microsof t.com...
Hi,
All images on my ASP.Net web site are reloaded almost each time I visit a
page. My chache setting on IE is set to Automatically. When I visit
another web site, images are rarely reloaded so it's fast. This slows down my site
and it's really a pain in the neck.
All my web pages are dynamic and are built from a database. There no meta
field or Response.Expires...
So I was wondering if ASP.Net has something to do with this? How can I
force images to be put in cache?
Test by yourself to see what I'm talking about: http://www.nuouz.com
Thanks for any help
Stephane