Is the site any faster?

[TerryMason]

You guys may have noticed that Jeepz.com hasn't been as snappy as it's younger days. Google said that it took an average of 9 seconds to load up each page (which as any teenager can tell you is forever..).

I've made a number of changes under the hood (I've setup a CDN for you tech types), and hopefully things will be a bit quicker around here.

Let me know if you see anything fishy, especially missing images.

 

[stumblnyj]

I have a slow modem so I never knew it was acting up. Thanks for the upgrade

 

[Mrsig]

It seem good to me. Thanks for all your hard work.

 

[carnuck]

fast, but not resolving all the links. I click on "new threads" and load all the outstanding pages since I was last on, but they don't finish loading, even 1/2 an hour later.

 

[TerryMason]

fast, but not resolving all the links. I click on "new threads" and load all the outstanding pages since I was last on, but they don't finish loading, even 1/2 an hour later.

That doesn't sound good. Are any images loading other than the Jeepz.com logo in the upper left?

Are you using this on a standard computer, or your phone / ipad, etc? If you're able to take a screenshot that would help a ton, if not could you describe what you see (i.e. X's for images, site looks weird).

 

[TerryMason]

Carnuck,
I talked to the datacenter guys, and they gave me a list of things to try. If you don't mind, could you check out the following:


1. go to http://debug-16.netdna-cdn.com and tell you what they see there
2. Do a traceroute for the CDN URL "img.jeepz.com (click on start, then in the run box type "cmd". In the black box that opens type in "traceroute img.jeepz.com" and paste the output here.
3. Go to an image URL Directly, i.e: http://img.jeepz.com/gallery/data/500/thumbs/2209410_10_full.jpg and let you know what they see there.

 

[carnuck]

1) You are hitting the NetDNA Los Angeles Datacenter




2) /usr/sbin/traceroute img.jeepz.com
traceroute to img.jeepz.com (108.161.189.3), 30 hops max, 40 byte packets using UDP
1 10.0.0.1 (10.0.0.1) 0.571 ms 0.571 ms 1.507 ms
2 73.98.12.1 (73.98.12.1) 10.900 ms 11.331 ms 13.327 ms
3 68.87.206.193 (68.87.206.193) 13.217 ms 12.369 ms 11.429 ms
4 ae-29-0-ar03.burien.wa.seattle.comcast.net (69.139.164.213) 11.760 ms 11.810 ms 14.023 ms
5 ae-1-0-ar03.seattle.wa.seattle.comcast.net (68.85.240.94) 12.664 ms 10.640 ms 10.678 ms
6 he-1-7-0-0-10-cr01.seattle.wa.ibone.comcast.net (68.86.91.165) 20.486 ms he-1-6-0-0-11-cr01.seattle.wa.ibone.comcast.net (68.86.92.33) 21.739 ms he-1-5-0-0-10-cr01.seattle.wa.ibone.comcast.net (68.86.94.57) 22.805 ms
7 pos-1-13-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.85.162) 36.421 ms 34.992 ms 34.384 ms
8 pos-1-10-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.250) 48.987 ms 48.971 ms 45.871 ms
9 pos-0-2-0-0-pe01.600wseventh.ca.ibone.comcast.net (68.86.87.154) 37.071 ms 38.541 ms 38.215 ms
10 173.167.57.138 (173.167.57.138) 44.639 ms 45.779 ms 44.850 ms
11 ae0-90g.cr1.lax1.us.nlayer.net (69.31.127.141) 39.208 ms 40.981 ms 40.123 ms
12 ae1-50g.ar1.lax2.us.nlayer.net (69.31.127.130) 43.236 ms 40.465 ms 38.360 ms
13 69.174.36.2 (69.174.36.2) 43.474 ms 42.522 ms 41.043 ms
14 108.161.189.3 (108.161.189.3) 39.590 ms 37.489 ms 39.479 ms


3)

It's fine now. I see Anonyrats have been taking down sites with DOS attacks.

 

[TerryMason]

It's fine now. I see Anonyrats have been taking down sites with DOS attacks.

Glad it's working. I've switched us to a content delivery network that is suppose to give you images & files from somewhere local (Jeepz.com is on a server in VA, but you're pulling images from LA). It looks like there was a blip in that system - I had them make a few changes and things seems to be straight now.

If you or anyone else sees problems (broken images, bad formatting, etc) either post here or email me (webmaster at jeepz).