Computer slow to access "new" or rarely-used sites

Discussion in 'Windows 7 Networking' started by billm, Jun 15, 2015.

  1. billm

    billm New Member

    Joined:
    Jun 15, 2015
    Messages:
    3
    Likes Received:
    0
    I have a fibre-based internet connexion and enjoy fast download speeds. Once internet pages have been accessed, pages download virtually instantly. The problem comes with gaining access to pages. If sites have not been used for a long time or ever before, browsers (generally Firefox) consistently seem to have to wait 30 seconds to 1 minute before downloading starts - the browsers reporting that they are waiting for the site to respond during this time. This effect does not occur with regularly used sites (presumably cach'd) such as Google where response after input of the address is virtually instantaneous. Can anyone suggest why this might be occurring and what I could do to limit the effect?
     
  2. Spirit Wolfe

    Spirit Wolfe Well-Known Member

    Joined:
    Mar 14, 2014
    Messages:
    38
    Likes Received:
    2
    Hello:

    Welcome. To answer this question is somewhat of a two-fold answer. It sounds like you have a static IP address (with a fibre optic & broadband connections - your service provider usually provides you with an IP address that doesn't change upon a reboot/reconnect to you service provider). Your browser has a cache that stores your web pages, static IP addresses utilize the same principles. Your IP address links your service provider's NameServer to the WWW (internet) well that server also has a cache as well. If the NAME (NOT its IP address YET) of the website that you are wanting to view (initially and for the FIRST time) cannot be "locally found" within your service provider's NameServers' (this is true for all forms of I-net connections) cache then it forwards your request to other NameServers that are not local to your service provider's NameServers. This spiderwebs out through the I-net until your request is found or a 404 error (server nor found) is returned to your web browser. Now it has been debated that knowing the ACTUAL IP ADDRESS rather than the NAME of ther website MIGHT return a faster response because computers will and can work better with numbers (IP addresses) than an actual name of a website. You see that delay you are experiencing is the multiple servers your ISP provider's computers (servers) are accessing to provide you with the answer you typed into your Awesome Bar (Firefox's fancy name for the URL bar) to bring your answer back to your computer. You see when you type the name of a website into your URL bar and there is no actual numerical IP address to tag along with that name of the website you asked for, the service provider's NameServers need to hunt for that NUMERICAL version of said IP. (Thus your slight delay.) If it cannot find said numerical IP address then the ISP's NameServers have no choice but to return a 404 error.

    I hope this helps and explains your question...

    Cheers!
     
  3. billm

    billm New Member

    Joined:
    Jun 15, 2015
    Messages:
    3
    Likes Received:
    0
    Thanks Shane for this. I can understand that a site which isn't cach'd on my pc or my service providers name servers will take a few seconds to "find" via the name/IP translation process but 30 seconds plus seems excessive. I don't remember it being this long with previous pcs or indeed my present pc a few months ago. I know its a different service provider but my iphone via my wifi and into my mobile provider's network and my ipad via wifi to the same as my pc don't take this long; hence my belief that there's something wrong (more likely software than hardware) within my pc.

    Regards

    Bill
     
  4. billm

    billm New Member

    Joined:
    Jun 15, 2015
    Messages:
    3
    Likes Received:
    0
    I may have found an answer but can't understand why! I have a Sonos system. Occasionally, one speaker on the Sonosnet network has stopped working and either that speaker or the Sonos controller has had to be re-booted. Sonos forums and Sonos themselves all suggest this is due to wireless interference. I have now checked wireless settings and found that both my broadband router and the Sonosnet were operating on Channel 11 - my surprise is that I hadn't had much more interference! I have now changed the Sonosnet to Channel 6 and so far have had no Sonos dropouts and previously unused websites (and ones you would not expect my service provider to cache) load at what I would call normal speeds. The real oddity is that my pc is connected by Cat 5 cable to a gigabit ethernet switch which, in turn, is connected to a gigabit port on my router so no wifi involved directly. How an apparent wifi interference issue can influence a cable-connected pc, I have no idea but maybe it's some problem with wifi tying up resources in the router? Work continues.
     

Share This Page

Loading...