Greetings!
More often then not, it takes longer than 20-30 seconds to connect to your page. When it does, the main page will sometimes have missing images, the font will change, etc..I copied an error I get pretty frequently:
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; Tablet PC 2.0; OfficeLiveConnector.1.5; OfficeLivePatch.1.3; Amazon Toolbar; .NET4.0C; AskTB5.6)
Timestamp: Sun, 25 Jul 2010 14:06:04 UTC
Message: Unspecified error.
Line: 145
Char: 186
Code: 0
URI: http://paizo.com/include/jquery.js
Message: Unspecified error.
Line: 145
Char: 186
Code: 0
URI: http://paizo.com/include/jquery.js
Any help would be greatly appreciated.
-Chronocypher
It might be a caching problem... Do you clear your cache routinely?
If not, you might want to give it a try.
I am guessing you are using an older version of Firefox? Your error says Mozilla 4.0 (and Firefox is up to Mozilla 5.0). You might want to consider updating. Anyway.
For Firefox look under Tools > Options > Privacy
Depending on your settings, you can see different things. Look for a link to "Clear History now" or something similar. Click on it, and you should get a dialog box with a list of items that can be check marked. Make sure Cache is checked (the other items can be checked, or not, as you see fit) and then click the "Clear Now" button at the bottom of the window.
Close all browser windows. Restart your browser, and try again.
Let me know if that works, and if not what browser you are using.
It might be a caching problem... Do you clear your cache routinely?
If not, you might want to give it a try.
I am guessing you are using an older version of Firefox? Your error says Mozilla 4.0 (and Firefox is up to Mozilla 5.0). You might want to consider updating. Anyway.
For Firefox look under Tools > Options > Privacy
Depending on your settings, you can see different things. Look for a link to "Clear History now" or something similar. Click on it, and you should get a dialog box with a list of items that can be check marked. Make sure Cache is checked (the other items can be checked, or not, as you see fit) and then click the "Clear Now" button at the bottom of the window.
Close all browser windows. Restart your browser, and try again.
Let me know if that works, and if not what browser you are using.
I'm actually using IE8. I tried what you suggested however for Firefox. Still sluggish on the pickup for Firefox as well.
Damn. The "broken pics" usually points to cache problems, and I was hoping that would clear up the sluggishness...
Clearing the cache on IE8, if you are interested.
But you appear to have a bit more intensive problem.
Is it only a problem on Paizo?
Unfortunately, there is a trend of not configuring servers properly on the 'net, so my usual bag of tricks to help figure out if it is local or not doesn't tend to work anymore...
We can try it though.
Open up a Command Prompt (under All Programs > Accessories) and type:
ping paizo.com
If it doesn't start a series of "Connection Timed Out" messages, what are the approximate times? (press Ctrl+c to stop the readout.)
The next step gets really involved, so I will wait and see if ping gives us any clues.
|
I posted this in another thread but thought it might be worth posting here as well ...
Many people are noticing the site's slow performance lately. I suspect that increased traffic due to Pathfinder's growing popularity might be part of the cause.
Unfortuately, as has been noted, the site seems to be getting slower and slower - almost to the point of being unusable in the late afternoon! I mean, it's getting REALLY bad!
My big concern (and I say this from an unabashed Paizo / Pathfinder fan's perspective) is that as more new people come to the site, especially when the APG comes out, many will be turned off and frustrated by the site's sometimes painfully slow performance lately and may just not return! And, as more and more new people come to the site, does that mean the performance issues will increase even more? I would hate for Paizo to lose potential new fans / customers due to the site's lack of speed. I really hope that Gary, Vic, Lisa and co. are putting as much of their already stretched resources into resolving the issue asap. I know GenCon is Priority One right now, but I think the slow web site should pretty much be Priority TWO.
Damn. The "broken pics" usually points to cache problems, and I was hoping that would clear up the sluggishness...
Clearing the cache on IE8, if you are interested.
But you appear to have a bit more intensive problem.
Is it only a problem on Paizo?
Unfortunately, there is a trend of not configuring servers properly on the 'net, so my usual bag of tricks to help figure out if it is local or not doesn't tend to work anymore...
We can try it though.
Open up a Command Prompt (under All Programs > Accessories) and type:
ping paizo.com
If it doesn't start a series of "Connection Timed Out" messages, what are the approximate times? (press Ctrl+c to stop the readout.)
The next step gets really involved, so I will wait and see if ping gives us any clues.
Tried pinging paizo.com Sent out 4 packets with 100% loss. (Request timed out)
I was afraid of that... I have the same problem. There seems to be one particular server in the Seattle area that doesn't work as it should...
Anyway.
Here is a bit more in depth explanation of tracert in case what I am about to explain isn't as clear as it should be.
Open up a command prompt again and type:
tracert paizo.com
This will probably take some time, and then "request timed out" somewhere near the Paizo servers.
As long as the first few lines are quick (times well under 200ms) it is very likely an external error. This does not mean it is a Paizo error. Just it isn't likely your computer or ISP.
Some things to look for:
The first and/or second output line could have '*' for times. This is very likely if you are using Comcast. (They are notorious for not setting up their servers properly.) You can ignore this.
If the first few "hops" are taking a long time, and the last part of the line (the destination/location part) has your ISP name in there somewhere, it suggests your ISP is having a problem. Give their tech support a call, and try working with them to resolve it.
If even the first few hops time out... There is something else going on.
I can try walking you through it, but I will need to know more about your internet setup. (Do you go through a router and/or other hardware firewall, do you share the connection with others, etc.) If it reaches this point, be prepared to give detailed (but personal information free) descriptions.
I was afraid of that... I have the same problem. There seems to be one particular server in the Seattle area that doesn't work as it should...
Anyway.
Here is a bit more in depth explanation of tracert in case what I am about to explain isn't as clear as it should be.
Open up a command prompt again and type:
tracert paizo.com
This will probably take some time, and then "request timed out" somewhere near the Paizo servers.
As long as the first few lines are quick (times well under 200ms) it is very likely an external error. This does not mean it is a Paizo error. Just it isn't likely your computer or ISP.
Some things to look for:
The first and/or second output line could have '*' for times. This is very likely if you are using Comcast. (They are notorious for not setting up their servers properly.) You can ignore this.
If the first few "hops" are taking a long time, and the last part of the line (the destination/location part) has your ISP name in there somewhere, it suggests your ISP is having a problem. Give their tech support a call, and try working with them to resolve it.
If even the first few hops time out... There is something else going on.
I can try walking you through it, but I will need to know more about your internet setup. (Do you go through a router and/or other hardware firewall, do you share the connection with others, etc.) If it reaches this point, be prepared to give detailed (but personal information free) descriptions.
Alright, at about hop 15 is when things go to garbage. Here's a copy of the Tracert you requested:
Tracing route to paizo.com [208.79.150.37]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 13 ms 7 ms 10.108.160.1
3 38 ms 19 ms 17 ms gig-7-1-0-101.orldflmbhe-rtr2.cfl.rr.com [24.95.
231.198]
4 18 ms 19 ms 17 ms 76.228.95.24.cfl.res.rr.com [24.95.228.76]
5 20 ms 19 ms 19 ms xe-11-3-0.bar1.Orlando1.Level3.net [4.79.116.137
]
6 17 ms 19 ms 17 ms ae-0-11.bar2.Orlando1.Level3.net [4.69.137.146]
7 61 ms 53 ms 53 ms ae-14-14.ebr1.Dallas1.Level3.net [4.69.137.154]
8 54 ms 53 ms 53 ms ae-62-68.ebr2.Dallas1.Level3.net [4.69.146.67]
9 77 ms 71 ms 72 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
10 66 ms 68 ms 71 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
11 100 ms 92 ms 104 ms ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
12 93 ms 92 ms 93 ms ae-23-52.car3.Seattle1.Level3.net [4.68.105.36]
13 94 ms 93 ms 93 ms WORLD-COMMU.car3.Seattle1.Level3.net [4.71.152.1
62]
14 93 ms 96 ms 94 ms 204.11.200.3
15 102 ms 117 ms 99 ms 204.11.204.250
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
My internet service provider is Bright House Networks via Roadrunner High Speed Internet.
I didn't ask for a copy, but that sure does make it easier.
Yeah, you hit the same "wall" in Seattle I do.
But your local hops are great. And your ISP hops are good.
So, this tells us that the problem isn't your connection on your end.
It isn't your browser, because you have the same connection issues with Firefox and IE...
Do you only have this sluggishness with Paizo? If so, it is probably the connection between you and Paizo.
If you have this problem with all pages, I think you either have malware or some configuration quirks. (That doesn't mean you did anything wrong, sometimes settings get weird on their own.)
Do you have anti-spyware/anti-virus installed? Have you run scans recently? What scanning programs are you using?
I didn't ask for a copy, but that sure does make it easier.
Yeah, you hit the same "wall" in Seattle I do.
But your local hops are great. And your ISP hops are good.
So, this tells us that the problem isn't your connection on your end.
It isn't your browser, because you have the same connection issues with Firefox and IE...
Do you only have this sluggishness with Paizo? If so, it is probably the connection between you and Paizo.
If you have this problem with all pages, I think you either have malware or some configuration quirks. (That doesn't mean you did anything wrong, sometimes settings get weird on their own.)Do you have anti-spyware/anti-virus installed? Have you run scans recently? What scanning programs are you using?
Actually, I have this issue with one other site: Dominos.com. Yes, I have Ad-aware, AVG 9.0, Ccleaner, and occasionally I run a program called Advanced System Care. I use both Ad-Aware and AVG to scan my computer for issues.
Well then...
I tried a tracert to Dominos.com, and hit another request timed out wall in the Washington area.
If those are the only two sites you have problems with (or any others you find are in the Washington area) I would say it is a network problem in that state.
EDIT:: Actually, the wall I find is in California. With Above.net. And this isn't the only issue with that section of servers.
It doesn't help you any... But at least you can know you aren't doing anything wrong and/or couldn't fix things anyway.