Web Page Display is Slow

[WMB]

Windows XP(Home) SP3, 32Bit, OE6, IE8; Plenty of RAM & HHD space. Continuous
checks for Virus/Malware

1.4Ghz, VIA Technologies, Inc. 8 kilobyte primary memory cache, 256 kilobyte
secondary memory cache, P4X266-8233, Enclosure Type: Desktop V2 Premier, 2
External USB 500/1TB Hard Drives (NTFS), 1.5 GB Ram, Upgraded PSU, Belarc
Advisor, Multimedia - lists, MPU-401 Compatible MIDI Device - Realtek AC'97
Audio for VIA (R) Audio Controller - Standard Game Port. Circuit Board:
P4X266-8233, Bus Clock: 100 megahertz, BIOS: Award Software International,
Inc. 6.00 PG 09/05/2001, Virus/Malware Protection - Windows Live One Care,
MS Windows Malicious SW Removal Tool, SUPERAntiSpyware, HiJackThis,
Malwarebyte Anti-Malware, Registry Mechanic 8.0.0.900, CCleaner.

Hi, while trying to glean info from these newsgroups and doing a poor job of
it, I encountered information I wanted to try regarding- web pages not being
displayed in IE. It was suggested by one the knowledgeable people trying to
help that the OP run a trace to a web site - www.yahoo.com. The results of
doing so was supposed to provide info that could be used to help the OP.
Well, I did it also and the results are below, but I have no idea what is
indicated by those results. Any help deciphering that info will sincerely
be appreciated. Thank you if you can help. I'm goggling "trace route" now.

My question from all this is, does it contain anything to indicate/verify
slow loading of web pages?

Microsoft Windows XP [Version 5.1.2600]
<c> copyright 1985-2001 Microsoft Corp.

CDocuments and Settings\WMB>tracert www.yahoo.com

Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 13 ms 11 ms 13 ms f1.www.vip.rel.yahoo.com
[69.147.76.15]

Trace complete.

cDocuments and Settings\WMB>

Thanks for any help

TIA

 

[Robert Aldwinckle]

"WMB" <brown.2005@.nospamcomcast.net> wrote in message news2sfj9MmKHA.2680@TK2MSFTNGP04.phx.gbl...

> [Subject: Web Page Display is Slow]



> CDocuments and Settings\WMB>tracert www.yahoo.com
>
> Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]


> My question from all this is, does it contain anything to indicate/verify
> slow loading of web pages?


When is it slow? Just at the beginning?

It might. That shows that the host name is an alias for a different
canonical name and that is confirmed by nslookup:

Non-authoritative answer:
Name: www-real.wa1.b.yahoo.com
Address: 69.147.76.15
Aliases: www.yahoo.com, www.wa1.b.yahoo.com

This would mean that there would never be a lookup with an IP address
cached (just the CNAM record) which could cause its lookup to be done
each time.

You could try to ping -n 1 the canonical name before starting IE
but it doesn't look like it would be cached long enough to matter.
E.g. after doing that ipconfig /displaydns shows:

<displaydns>
www-real.wa1.b.yahoo.com
----------------------------------------
Record Name . . . . . : www-real.wa1.b.yahoo.com
Record Type . . . . . : 1
Time To Live . . . . : 33
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 69.147.76.15
</displaydns

which would only give you 33 seconds of benefit for helping IE
with its lookups.

This really should only matter if you can't get connected at all
or if you are slow getting connected (e.g. if you have to retry
at least once) because supposedly once IE has made a connection
it will cache the IP address for a much longer period of time
(effectively as long as the iexplore.exe task is running in most cases.)

So, if your problem is just with *starting* at www.yahoo.com
all the above would suggest that you might get some improvement
by doing this (in a cmd window) first:

ping -n 1 www-real.wa1.b.yahoo.com


HTH

Robert Aldwinckle
---

 

[WMB]

"Robert Aldwinckle" <robald@techemail.com> wrote in message
newsE4DL0RmKHA.5728@TK2MSFTNGP06.phx.gbl...
>
> "WMB" <brown.2005@.nospamcomcast.net> wrote in message
> news2sfj9MmKHA.2680@TK2MSFTNGP04.phx.gbl...
>
>> [Subject: Web Page Display is Slow]
>
>
>
>> CDocuments and Settings\WMB>tracert www.yahoo.com
>>
>> Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]
>
>
>> My question from all this is, does it contain anything to indicate/verify
>> slow loading of web pages?
>
>
> When is it slow? Just at the beginning?
>
> It might. That shows that the host name is an alias for a different
> canonical name and that is confirmed by nslookup:
>
> Non-authoritative answer:
> Name: www-real.wa1.b.yahoo.com
> Address: 69.147.76.15
> Aliases: www.yahoo.com, www.wa1.b.yahoo.com
>
> This would mean that there would never be a lookup with an IP address
> cached (just the CNAM record) which could cause its lookup to be done
> each time.
>
> You could try to ping -n 1 the canonical name before starting IE
> but it doesn't look like it would be cached long enough to matter.
> E.g. after doing that ipconfig /displaydns shows:
>
> <displaydns>
> www-real.wa1.b.yahoo.com
> ----------------------------------------
> Record Name . . . . . : www-real.wa1.b.yahoo.com
> Record Type . . . . . : 1
> Time To Live . . . . : 33
> Data Length . . . . . : 4
> Section . . . . . . . : Answer
> A (Host) Record . . . : 69.147.76.15
> </displaydns
>
> which would only give you 33 seconds of benefit for helping IE
> with its lookups.
>
> This really should only matter if you can't get connected at all
> or if you are slow getting connected (e.g. if you have to retry
> at least once) because supposedly once IE has made a connection
> it will cache the IP address for a much longer period of time
> (effectively as long as the iexplore.exe task is running in most cases.)
>
> So, if your problem is just with *starting* at www.yahoo.com
> all the above would suggest that you might get some improvement
> by doing this (in a cmd window) first:
>
> ping -n 1 www-real.wa1.b.yahoo.com
>
>
> HTH
>
> Robert Aldwinckle
> ---

Hi, and thanks for replying. Yes, so slow on startup of IE8 and the loading
of my Home Page. Below is the result of "ping -n 1
www-real.wa1.b.yahoo.com". Its copy & paste from DOS window. That's why I
love these newsgroups, you can/have to learn so much.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

CDocuments and Settings\WMB>ping -n 1 www=real.wa1.b.yahoo.com
Ping request could not find host www=real.wa1.b.yahoo.com. Please check the
name
and try again.

CDocuments and Settings\WMB>cd\

C>ping -n1 www-real.wa1.b.yahoo.com
Bad value for option -n1, valid range is from 1 to 4294967295.

C>ping -n 1 www-real.wa1.b.yahoo.com

Pinging www-real.wa1.b.yahoo.com [69.147.76.15] with 32 bytes of data:

Reply from 69.147.76.15: bytes=32 time=14ms TTL=55

Ping statistics for 69.147.76.15:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 14ms, Average = 14ms

C>

 

[Robert Aldwinckle]

"WMB" <brown.2005@.nospamcomcast.net> wrote in message news:e0xsI5UmKHA.2160@TK2MSFTNGP02.phx.gbl...

> Pinging www-real.wa1.b.yahoo.com [69.147.76.15] with 32 bytes of data:


That's the only part of the ping you want to care about.
It means that you have loaded a lookup for your host's name's alias.
Then you don't have to go back to your DNS for as long as the
Time To Live (TTL) indicates.

Use ipconfig /displaydns >displaydns.txt
and notepad displaydns.txt to check on how much time you have
to let IE take advantage of the benefit.

So, did you get IE started any smoother after trying this? ; )


HTH

Robert
---

 

[Dan]

"WMB" <brown.2005@.nospamcomcast.net> wrote in message
news2sfj9MmKHA.2680@TK2MSFTNGP04.phx.gbl...
> Windows XP(Home) SP3, 32Bit, OE6, IE8; Plenty of RAM & HHD space.
> Continuous checks for Virus/Malware
>
> 1.4Ghz

Is this the CPU speed? If so, that's quite a slow system these days,
especially if you got all those virus/malware checks running at the same
time

> Microsoft Windows XP [Version 5.1.2600]
> <c> copyright 1985-2001 Microsoft Corp.
>
> CDocuments and Settings\WMB>tracert www.yahoo.com
>
> Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]
>
> 1 * * * Request timed out.
> 2 * * * Request timed out.
> 3 * * * Request timed out.
> 4 * * * Request timed out.
> 5 * * * Request timed out.
> 6 * * * Request timed out.
> 7 * * * Request timed out.
> 8 * * * Request timed out.
> 9 * * * Request timed out.
> 10 * * * Request timed out.
> 11 * * * Request timed out.
> 12 * * * Request timed out.
> 13 13 ms 11 ms 13 ms f1.www.vip.rel.yahoo.com
> [69.147.76.15]


That's not what I'd expect to see. All those asterisks mean there was no
response from that hop on the route, or that your router/firewall/security
application blocked out the response. That might well point to a networking
problem, and could be related to IE8 being slow to load. You should have a
list of various routers between you and the Yahoo server upstream router
showing in that list, eg. here's mine:

Tracing route to f1.www.vip.re1.yahoo.com [69.147.76.15]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.10.1
2 11 ms 14 ms 11 ms ip129.net92-244-171.ci-net.com
[92.244.171.129]
3 10 ms 10 ms 9 ms gi5-1.r1.thn.core.as8844.net [195.72.160.70]
4 10 ms 10 ms 10 ms ge-3-3-0.pat1.tc2.yahoo.com [195.66.226.129]
5 12 ms 10 ms 11 ms ge-2-0-0.pat1.the.yahoo.com [66.196.65.0]
6 115 ms 113 ms 114 ms so-1-0-0.pat1.nyc.yahoo.com [66.196.65.13]
7 114 ms 112 ms 108 ms so-3-0-0.pat1.dcp.yahoo.com
[216.115.101.157]
8 108 ms 109 ms 109 ms ae2-p170.msr2.re1.yahoo.com [216.115.108.69]
9 108 ms 106 ms 107 ms te-9-4.bas-a1.re1.yahoo.com [66.196.112.207]
10 107 ms 108 ms 108 ms f1.www.vip.re1.yahoo.com [69.147.76.15]

Trace complete.

My list will be different to yours because I'm in a different location than
you, and so the list of routers my connection goes through will be mostly
different. Also my response times are worse because that server is over the
transatlantic. However, note that all the router names from DNS are showing
up along with their IPs.

I'm guessing that you have a DNS resolution problem. Is your PC using DHCP
from a router/modem? If so, is it using the router/modem IP for DNS
handling? Easy way to check is to run

ipconfig /all

and look at the DNS settings. If they are set to the IP address of your
router/modem, then your PC is relying on a DNS proxy in the router firmware.
If it's anything like my Netgear it's unstable at best, and after a couple
of hours of running is pretty much useless. Take the DNS server IP addresses
that your router/modem is using and manually assign them to your network
settings, that way Windows is connecting to your ISP DNS servers directly
and will likely get a much quicker response for addresses that are not yet
in the lcoal DNS client cache.

--
Dan

 

[WMB]

"Dan" <news@worldofspack.com> wrote in message
news:709D5361-7F11-40AE-B931-9A3E07F6FFFC@microsoft.com...
>
> "WMB" <brown.2005@.nospamcomcast.net> wrote in message
> news2sfj9MmKHA.2680@TK2MSFTNGP04.phx.gbl...
>> Windows XP(Home) SP3, 32Bit, OE6, IE8; Plenty of RAM & HHD space.
>> Continuous checks for Virus/Malware
>>
>> 1.4Ghz
>
> Is this the CPU speed? If so, that's quite a slow system these days,
> especially if you got all those virus/malware checks running at the same
> time
>
>> Microsoft Windows XP [Version 5.1.2600]
>> <c> copyright 1985-2001 Microsoft Corp.
>>
>> CDocuments and Settings\WMB>tracert www.yahoo.com
>>
>> Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]
>>
>> 1 * * * Request timed out.
>> 2 * * * Request timed out.
>> 3 * * * Request timed out.
>> 4 * * * Request timed out.
>> 5 * * * Request timed out.
>> 6 * * * Request timed out.
>> 7 * * * Request timed out.
>> 8 * * * Request timed out.
>> 9 * * * Request timed out.
>> 10 * * * Request timed out.
>> 11 * * * Request timed out.
>> 12 * * * Request timed out.
>> 13 13 ms 11 ms 13 ms f1.www.vip.rel.yahoo.com
>> [69.147.76.15]
>
>
> That's not what I'd expect to see. All those asterisks mean there was no
> response from that hop on the route, or that your router/firewall/security
> application blocked out the response. That might well point to a
> networking problem, and could be related to IE8 being slow to load. You
> should have a list of various routers between you and the Yahoo server
> upstream router showing in that list, eg. here's mine:
>
> Tracing route to f1.www.vip.re1.yahoo.com [69.147.76.15]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms 10.1.10.1
> 2 11 ms 14 ms 11 ms ip129.net92-244-171.ci-net.com
> [92.244.171.129]
> 3 10 ms 10 ms 9 ms gi5-1.r1.thn.core.as8844.net
> [195.72.160.70]
> 4 10 ms 10 ms 10 ms ge-3-3-0.pat1.tc2.yahoo.com
> [195.66.226.129]
> 5 12 ms 10 ms 11 ms ge-2-0-0.pat1.the.yahoo.com [66.196.65.0]
> 6 115 ms 113 ms 114 ms so-1-0-0.pat1.nyc.yahoo.com [66.196.65.13]
> 7 114 ms 112 ms 108 ms so-3-0-0.pat1.dcp.yahoo.com
> [216.115.101.157]
> 8 108 ms 109 ms 109 ms ae2-p170.msr2.re1.yahoo.com
> [216.115.108.69]
> 9 108 ms 106 ms 107 ms te-9-4.bas-a1.re1.yahoo.com
> [66.196.112.207]
> 10 107 ms 108 ms 108 ms f1.www.vip.re1.yahoo.com [69.147.76.15]
>
> Trace complete.
>
> My list will be different to yours because I'm in a different location
> than you, and so the list of routers my connection goes through will be
> mostly different. Also my response times are worse because that server is
> over the transatlantic. However, note that all the router names from DNS
> are showing up along with their IPs.
>
> I'm guessing that you have a DNS resolution problem. Is your PC using DHCP
> from a router/modem? If so, is it using the router/modem IP for DNS
> handling? Easy way to check is to run
>
> ipconfig /all
>
> and look at the DNS settings. If they are set to the IP address of your
> router/modem, then your PC is relying on a DNS proxy in the router
> firmware. If it's anything like my Netgear it's unstable at best, and
> after a couple of hours of running is pretty much useless. Take the DNS
> server IP addresses that your router/modem is using and manually assign
> them to your network settings, that way Windows is connecting to your ISP
> DNS servers directly and will likely get a much quicker response for
> addresses that are not yet in the lcoal DNS client cache.
>
> --
> Dan

Hello Dan, below is what I get after running "ipconfig /all" on my computer.
Do you notice anything wrong or that should be different. Thanks


Microsoft Windows XP [Version 5.1.
2600]
(C) Copyright 1985-2001 Microsoft Corp.

CDocuments and Settings\WMB>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : home-748bce7cc8
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : chn.comcast.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : chn.comcast.net
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Eth
ernet NIC
Physical Address. . . . . . . . . : 00-D0-09-FD-05-67
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 68.87.73.246
68.87.71.230
Lease Obtained. . . . . . . . . . : Wednesday, January 20, 2010
7:24:54
PM
Lease Expires . . . . . . . . . . : Wednesday, January 20, 2010
8:24:54
PM

CDocuments and Settings\WMB>

 

[Dan]

"WMB" <brown.2005@.nospamcomcast.net> wrote in message
news:#TNCuVjmKHA.1540@TK2MSFTNGP06.phx.gbl...
> "Dan" <news@worldofspack.com> wrote in message
> news:709D5361-7F11-40AE-B931-9A3E07F6FFFC@microsoft.com...
>>
>> "WMB" <brown.2005@.nospamcomcast.net> wrote in message
>> news2sfj9MmKHA.2680@TK2MSFTNGP04.phx.gbl...
>>> Windows XP(Home) SP3, 32Bit, OE6, IE8; Plenty of RAM & HHD space.
>>> Continuous checks for Virus/Malware
>>>
>>> 1.4Ghz
>>
>> Is this the CPU speed? If so, that's quite a slow system these days,
>> especially if you got all those virus/malware checks running at the same
>> time
>>
>>> Microsoft Windows XP [Version 5.1.2600]
>>> <c> copyright 1985-2001 Microsoft Corp.
>>>
>>> CDocuments and Settings\WMB>tracert www.yahoo.com
>>>
>>> Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]
>>>
>>> 1 * * * Request timed
>>> out.
>>> 2 * * * Request timed
>>> out.
>>> 3 * * * Request timed
>>> out.
>>> 4 * * * Request timed
>>> out.
>>> 5 * * * Request timed
>>> out.
>>> 6 * * * Request timed
>>> out.
>>> 7 * * * Request timed
>>> out.
>>> 8 * * * Request timed
>>> out.
>>> 9 * * * Request timed
>>> out.
>>> 10 * * * Request timed out.
>>> 11 * * * Request timed out.
>>> 12 * * * Request timed out.
>>> 13 13 ms 11 ms 13 ms f1.www.vip.rel.yahoo.com
>>> [69.147.76.15]
>>
>>
>> That's not what I'd expect to see. All those asterisks mean there was no
>> response from that hop on the route, or that your
>> router/firewall/security application blocked out the response. That might
>> well point to a networking problem, and could be related to IE8 being
>> slow to load. You should have a list of various routers between you and
>> the Yahoo server upstream router showing in that list, eg. here's mine:
>>
>> Tracing route to f1.www.vip.re1.yahoo.com [69.147.76.15]
>> over a maximum of 30 hops:
>>
>> 1 <1 ms <1 ms <1 ms 10.1.10.1
>> 2 11 ms 14 ms 11 ms ip129.net92-244-171.ci-net.com
>> [92.244.171.129]
>> 3 10 ms 10 ms 9 ms gi5-1.r1.thn.core.as8844.net
>> [195.72.160.70]
>> 4 10 ms 10 ms 10 ms ge-3-3-0.pat1.tc2.yahoo.com
>> [195.66.226.129]
>> 5 12 ms 10 ms 11 ms ge-2-0-0.pat1.the.yahoo.com [66.196.65.0]
>> 6 115 ms 113 ms 114 ms so-1-0-0.pat1.nyc.yahoo.com [66.196.65.13]
>> 7 114 ms 112 ms 108 ms so-3-0-0.pat1.dcp.yahoo.com
>> [216.115.101.157]
>> 8 108 ms 109 ms 109 ms ae2-p170.msr2.re1.yahoo.com
>> [216.115.108.69]
>> 9 108 ms 106 ms 107 ms te-9-4.bas-a1.re1.yahoo.com
>> [66.196.112.207]
>> 10 107 ms 108 ms 108 ms f1.www.vip.re1.yahoo.com [69.147.76.15]
>>
>> Trace complete.
>>
>> My list will be different to yours because I'm in a different location
>> than you, and so the list of routers my connection goes through will be
>> mostly different. Also my response times are worse because that server is
>> over the transatlantic. However, note that all the router names from DNS
>> are showing up along with their IPs.
>>
>> I'm guessing that you have a DNS resolution problem. Is your PC using
>> DHCP from a router/modem? If so, is it using the router/modem IP for DNS
>> handling? Easy way to check is to run
>>
>> ipconfig /all
>>
>> and look at the DNS settings. If they are set to the IP address of your
>> router/modem, then your PC is relying on a DNS proxy in the router
>> firmware. If it's anything like my Netgear it's unstable at best, and
>> after a couple of hours of running is pretty much useless. Take the DNS
>> server IP addresses that your router/modem is using and manually assign
>> them to your network settings, that way Windows is connecting to your ISP
>> DNS servers directly and will likely get a much quicker response for
>> addresses that are not yet in the lcoal DNS client cache.
>>
>> --
>> Dan
>
> Hello Dan, below is what I get after running "ipconfig /all" on my
> computer. Do you notice anything wrong or that should be different. Thanks
>
>
> Microsoft Windows XP [Version 5.1.
> 2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> CDocuments and Settings\WMB>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : home-748bce7cc8
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : chn.comcast.net
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : chn.comcast.net
> Description . . . . . . . . . . . : Realtek RTL8139/810x Family
> Fast Eth
> ernet NIC
> Physical Address. . . . . . . . . : 00-D0-09-FD-05-67
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.0.3
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.1
> DHCP Server . . . . . . . . . . . : 192.168.0.1
> DNS Servers . . . . . . . . . . . : 68.87.73.246
> 68.87.71.230
> Lease Obtained. . . . . . . . . . : Wednesday, January 20, 2010
> 7:24:54
> PM
> Lease Expires . . . . . . . . . . : Wednesday, January 20, 2010
> 8:24:54
> PM
>
> CDocuments and Settings\WMB>


That looks fine - the DNS server IPs are not the same as the gateway which
would have indicated that you were using a DNS proxy on the router/modem.

The only other thing I could suggest is to make sure that TCP Checksum
Offload handling is disabled - I've had Realtek onboards NICs suffer
performance due to this before, disabling it can in some cases improve
performance.

I still think this is more a networking issue rather than a browser issue.
You might be better off posting in a Windows networking group.

--
Dan