Check your equipment
Bottlenecks can happen on the Internet just as they do on roads. Between you and the website or server you are trying to access there are many other pieces of hardware that help move data back and forth. Thousands of other users are likely using these same pathways at the same time as you. In some cases, too much traffic can get caught in a spot where there is limited bandwidth, or where there are not enough alternative pathways to resort to. Sometimes mistakes or hardware failures can cause traffic to be routed along a longer path.
The first source of a bottleneck could be right in your own home. Checking the speed between you and your router or modem is simple. Click Start (or the Windows logo) and then run. In the dialog box that pops up, type in cmd and press enter. This should bring up a command prompt window. In this window, type ipconfig /all and press enter. A lot of information will appear, but only one line is of interest to us right now. In the command prompt window, locate the line that begins with Default Gateway. Write down the number that appears to the right.
We're going to use a utility called ping, which basically sends a message to a location and waits for the response. The time between sending the message and receiving the response is measured in milliseconds (ms). Response times of 150ms or lower are generally considered good. Response times of 500ms or higher are indications that there is an issue along the pathway, or that the server may be in a very distant location. Since you are within walking distance of your modem or router, your response time should be under 10ms. To find out, simply type ping followed by the number you wrote down earlier and press enter.
You're looking for the end of the report, where it displays the minimum, maximum, and average round-trip times. If they fall within a reasonable range- around or under 10ms- then the problem lies elsewhere. If the response time is higher try unplugging the modem, router, or access point and wait one minute before plugging it back in. If this hasn't resolved the problem, then you should contact your ISP, if they installed the equipment, or the device manufacturer.