Slow loading page seems to be getting worse.
The top part of the page usually pops up right away but doesn't want to finish.
I've tried turning off just about everything in start up and services.

http://www.chevelles.com/showroom/data/500/medium/screenshot3.jpg

Sometimes it takes forever for the green bars at the bottom to go all the way across, sometimes with maybe only a couple of green bars.
IE seems to be a little worse than Firefox.

using Windows XP Pro

Any ideas of what to try ?

I tried to edit this and it set there for a good two minutes so I shut down the broswer and started over.

Are you clean of Spyware?
Spybot S&D and Ad-Aware have helped in these cases.

This test can uncover config issues sometimes.
http://www.dslreports.com/tweaks

Embedded page links to busy ad servers can delay page loads too.

Sounds like you've made a good attempt at whats running or not.
I like to use msconfig to identify and shutdown unknown / unneeded processes.

I havent ran Spybot S&D or Ad-Aware for a while, I guess I never thought of that. :o
I did run ewido anti-malware a while back.
I'll try running those.

I never know which of all that stuff I can stop and what I need in msconfig.
Funny thing is it'll do this for a few days then all of a sudden everything loads fine for a while.

http://www.dslreports.com/tweakr/block:21873c7?service=cable&speed=&os=winXP&via=normal

Hi Dean. I ran a trace from the server to you and there seems to be a problem with some routing inside pccwbtn.net

Note: some routers do not respond to traces, but the ones before and after the *** are in the same network so it seems to be a routing problem to me. Plus I tried other locations through part of the same route and they all responded fast.

You may have a different route TO us depending on too many things to figure out, but I repeated this a couple of times with the same results.

In short, probably nothing you can do until it clears up on it's own. Might be congestion or ? Perhaps someone else can offer more insight on this.

Our server loads are great and response time is typically very fast.

Sometimes memory and processor speed will delay a "table" from being displayed as it has to be all handled before showing onscreen. The forums are just that, big tables. I think you said you had fast machines with enough memory, but it's worth mentioning in case anyone else is reading this.

You can try a trace with XP pro, by clicking on "start" then "run" and type this in the window that comes up:

tracert chevelles.com

look for *'s and/or slow response times.

Here is FROM us To you.

2 209.50.254.70 (209.50.254.70) 0.627 ms 1.345 ms 0.821 ms
3 ge3-0.cr02.vna01.pccwbtn.net (63.218.97.137) 0.602 ms 0.568 ms 0.488 ms
4 * * *
5 * * *
6 pos4-1.br02.ash01.pccwbtn.net (63.218.44.50) 1.500 ms 1.344 ms 1.326 ms
MPLS Label=24 CoS=0 TTL=127 S=0
7 pop1-ash-G2-2-6.atdn.net (66.185.139.105) 1.644 ms 1.594 ms 1.638 ms
8 bb2-ash-P0-0.atdn.net (66.185.144.194) 1.575 ms 1.683 ms 1.625 ms
MPLS Label=95 CoS=0 TTL=127 S=0
9 bb2-cin-P3-0.atdn.net (66.185.153.61) 30.457 ms 30.528 ms 30.294 ms
MPLS Label=61 CoS=0 TTL=127 S=0
10 bb1-cin-P2-0.atdn.net (66.185.153.48) 30.334 ms 30.267 ms 30.283 ms
MPLS Label=76 CoS=0 TTL=127 S=0
11 bb1-chi-P3-0.atdn.net (66.185.153.50) 30.402 ms 46.519 ms 30.445 ms
MPLS Label=18 CoS=0 TTL=127 S=0
12 pop1-chi-P0-0.atdn.net (66.185.141.85) 30.268 ms 30.350 ms 30.324 ms
13 rr-kansascity.atdn.net (66.185.141.94) 30.505 ms 30.510 ms 30.566 ms
14 so-3-1-0.kscymoL3-rtr1.kc.rr.com (24.94.160.162) 40.645 ms 40.535 ms pos8-0.kscymordc-rtr3.kc.rr.com (24.94.160.6) 40.808 ms
15 srp0-0.kscymordc-rtr1.kc.rr.com (24.94.160.195) 40.937 ms pos8-0.kscymordc-rtr4.kc.rr.com (24.94.160.2) 41.071 ms pos10-0.kscymordc-rtr4.kc.rr.com (24.94.160.170) 40.793 ms
16 srp0-0.kscymordc-rtr2.kc.rr.com (24.94.160.196) 40.930 ms 40.963 ms srp1-1.kscyksfloy-rtr1.kc.rr.com (24.31.239.9) 43.058 ms
17 srp1-1.kscyksfloy-rtr1.kc.rr.com (24.31.239.9) 42.618 ms gig0-2.kscyksfloy-ubr1.kc.rr.com (24.94.164.150) 43.365 ms 43.531 ms
18 gig0-2.kscyksfloy-ubr1.kc.rr.com (24.94.164.150) 43.446 ms gig0-2.kscyksfloy-ubr1.kc.rr.com (24.94.164.150) 43.097 ms

ps, I tried one to you from my home machine to your IP and the path was fast and clear.

Tracert stops at the end of the first line for quite a long while then starts up again and goes to the end quick and poof it's gone.
How do you save it?

Funny thing is, at the time I'm having this problem I can use another machine setting here that's connected to the same router and it never slows down.
:confused: