Hi,

I have a question I hope someone can give me some insight. I have a school email for my job. There are two ways to access it. Either from school, through their main system on our computer there. You click on the link on the menu of the computer and it loads right away.

Or you can on the internet and connect through a web link. This page loads slowly. Okay only 15 seconds or so but slower than the almost instant access at school.

One time I clicked on STOP on my browser, and then, re-clicked on the link to the page (saved on my favorites menu). The page loaded right away!

I've tried this when I have been away from the email, when it normally would take longer to load and each time it loads right away.

Has anyone experienced this? Now, I am thinking of how this is really random and maybe no one has had this experience.

Thanks in advance any insight you can give me!

**Editing to clarify what I'm wanting. I.E. A question!

Why is this website affected by my clicking on stop loading (the red x) function on my browser? It does seem to "remind" the computer of the website address. Why?

I do that on here as well, Joy, when a page is taking forever to load. I hit 'stop' and 'refresh' and it kicks it back into gear every time. I discovered this well over a year ago when FT began having a lot of freeze-up problems and do it all the time with my e-mail and any other site that seems to be lagging behind.

As far as answering your question 'why' it does this, I am not sure, but it may have something to do with the number of cookies and temporary files stored that the computer is trying to wade through. Whenever I begin experiencing this now, I go in and clean out my browser's cache.

It could also be that the page was loading, so when you hit 'stop' and reload the page, your web browser grabs what it had just been loaded because it's already on your computer.

I believe what is happening is that certain components are prevented from loading. For example some sites like my G-Mail account for example allow me to load only the HTML. It's basically the 'plain Jane' version. It's possible that's what's happening when you hit the Red X you're simple getting the necessities.

If I had to have a guess (and I will qualify that I am not a network engineer!) this behaviour may be caused by the way that the internet works.

A rough and ready lesson: information travels in small packets - when you click on a link, your computer sends a packet or two of information to the website's server, saying you want to see their page. In return, the website starts sending back a stream of packets that make up the information of the web page.

All well and good so far?

Well, what can happen, is that not all the packets make it. Some of them get lost. Somewhere. In the ether. But your computer knows it wants them, so it sits and waits for them.

And here is where my understanding gets a little spotty, and where someone more educated than I may be able to fill in the blanks. I'm pretty sure that if it's been waiting for a while, your computer is meant to let the site know that it has missed a packet, and that it wants it again. For some reason, this may be taking longer than it should.

When you click stop and reload, then it automatically asks for the packets again, so the stream starts again.

That may or may not all make sense...