Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a website that is occasionally slow loading. I'm not referring to the download speed. But sometimes Firefox's status will sit at "Waiting for" for 15-20 seconds. After the wait period, it loads quite fast. Is this because of DNS? My DNS host is (free account).

Thanks for helping a newbie out.

share|improve this question

This is not a DNS issue. If it was stuck at Looking up that would likely be a DNS problem.

If it was Connecting to it means your server wasn't responding at all, but with Waiting for there's definitely a problem somewhere, perhaps an Apache misconfiguration.

share|improve this answer
It's on a Windows 2008 machine. – Chris Feb 9 '10 at 23:42

Install something like Fiddler or YSlow, and watch it as you try to load the sites you have problems with.

share|improve this answer
..Or firebug. Nice extension, btw – sntg Feb 9 '10 at 23:26
up vote 0 down vote accepted

The issue was with the the Application pool worker process. Since my website was very new and I was the only one visiting it, occasionally the worker process would shut down if it wasn't active after 20 minutes. So it took some time to start up again when I would visit it.

In IIS, right click the specific application pool and select properties. Under performance, you can change the idle timeout.

share|improve this answer

Within most browsers you can enable a "status bar" at the bottom. This is an option under the "view" menu at the top. Once done it will tell you the current status of a page you are requesting. If it is in fact being delayed by a DNS lookup then you will see something like "Looking up:" for an extended period.

You can also perform some lookups via the command prompt to get an idea of how fast they are being performed.

start -> run -> cmd -> nslookup


terminal -> dig

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.