How can I shorten the wait times.
-
TERRIBLE wait times for s0.wp.com, s1.wp.com, s2.wp.com, and some others (e.g., 0.gravatar.com, google.com, et al.) I posted this in the forum some days ago, question was ignored.
I am use OS X Yosemite, latest version of Firefox and Chrome.
The wait for s0.wp.com and the others is often more than 1 minute by the clock.
Why are the wait times so terrible? It makes blogging quite difficult.
The blog I need help with is: (visible only to logged in users)
-
Hello there,
It sounds as if you’re having network problems. We do not have the same servers as Google, and the fact that you’re having slow load times for all these sites leads me to believe you need to talk to your Internet Service Provider.
FYI — We are able to open your blog and you Gravatar account very quickly. There aren’t any problems with those sites on our end.
Please let me know how that conversation goes, and if I can help further.
Thank you!
-
I just did a speed test: download speed is 21.71 Mbps and upload speed is 1.0 Mbps. And I get most sites quite quickly—indeed, the browser goes immediately to s0.wp.com and then it hangs there, often for more than a minute. Same sorts of delays on s1.wp.com, s2.wp.com, 0.gravatar.com, and things like fonts.googlesapis and the like. (I don’t have the exact names for those.) It’s as if s0.wp.com is simply hanging and not responding.
It’s worse on Firefox than Chrome, which suggests that it may be a problem here, but OTOH Chrome also seems to wait at times.
The version of Firefox is new, maybe it’s gummed up…
Okay. Thanks for the response.
-
Hi again,
I think it’s worth checking in with your ISP, but we’re still happy to do what we can on our end. Could you answer some questions for us:
- Who is your ISP?
- What is your IP? (Visit https://www.google.com/#q=whats+my+ip)
- Can you visit these four sites and let me know if you can access any of them?
Also, that’s interesting about Firefox being more cumbersome than Chrome. Good information to have. Thanks.
-
1. My ISP is AT&T U-Verse, and though AT&T does throttle bandwidth (illegally) for some users, I believe the focus of their misdeeds are mobile users, and I’m using a MacBook Pro.
2. My IP is 2602:306:bcdc:92e0:11ab:db83:97d0:7544
3. http://dfw.wordpress.com/ – connected immediately
http://sat.wordpress.com/ – connected immediately
http://iad.wordpress.com/ – connected immediately
http://wordpress.com/ – connected immediatelyI’ll continue using it and report if the problem persists.
-
-
Are you having trouble loading sites here at WordPress.com and that’s why you’re looking at your speeds to access s1.wp.com? Knowing what you’re having trouble loading (because no one really visits s1.wp.com directly, there’s nothing there) could help us figure out if this is an issue on our end.
You also mentioned that you’re having similar speed issues visiting Google, which indicates that this is likely a larger issue with your connection or ISP.
-
All sites load briskly except when I try to do something on WordPress.com: save a post, click “New Post,” etc. Any action I take ends up being a 1-2 minute wait, and I see “waiting for x” notes, where x is variously s0.wp.com, s1.wp.com, s2.wp.com, 0.gravatar.com, fonts.googleapis.com. Mostly, though, the wait (typically 1 minute) occurs while waiting for sn.wp.com, n being 0, 1, or 2.
This happens in Firefox, only when working in WordPress.com. In Chrome, it happens but less frequently.
My download speed in a speed test is 21 Mbps. My upload speed is 1 Mbps. I don’t know that it is the ISP, especially given that other sites work fine.
-
Can you please run these two commands in your Terminal and copy and paste the results of both for me:
ping -c 100 leisureguy.wordpress.comping -c 100 s1.wp.com -
Some of the responses from the first:
64 bytes from 192.0.78.13: icmp_seq=0 ttl=53 time=44.171 ms
64 bytes from 192.0.78.13: icmp_seq=1 ttl=53 time=57.491 ms
64 bytes from 192.0.78.13: icmp_seq=2 ttl=53 time=43.101 ms
64 bytes from 192.0.78.13: icmp_seq=3 ttl=53 time=43.752 ms
64 bytes from 192.0.78.13: icmp_seq=4 ttl=53 time=53.039 ms
64 bytes from 192.0.78.13: icmp_seq=5 ttl=53 time=47.248 ms
64 bytes from 192.0.78.13: icmp_seq=6 ttl=53 time=49.153 msSome of the responses from the second:
64 bytes from 72.21.91.111: icmp_seq=0 ttl=55 time=23.481 ms
64 bytes from 72.21.91.111: icmp_seq=1 ttl=55 time=24.369 ms
64 bytes from 72.21.91.111: icmp_seq=2 ttl=55 time=23.299 ms
64 bytes from 72.21.91.111: icmp_seq=3 ttl=55 time=24.763 ms
64 bytes from 72.21.91.111: icmp_seq=4 ttl=55 time=24.076 ms
64 bytes from 72.21.91.111: icmp_seq=5 ttl=55 time=26.727 ms
64 bytes from 72.21.91.111: icmp_seq=6 ttl=55 time=25.514 ms
64 bytes from 72.21.91.111: icmp_seq=7 ttl=55 time=24.316 ms
64 bytes from 72.21.91.111: icmp_seq=8 ttl=55 time=24.147 ms
64 bytes from 72.21.91.111: icmp_seq=9 ttl=55 time=23.686 ms
64 bytes from 72.21.91.111: icmp_seq=10 ttl=55 time=26.860 msToday it has been irregular: when I click “Add new” it mostly moves quickly, but one time there was a wait of over a minute for s1.wp.com. The message that appears at lower left is “Connecting to s1.wp.com” and then things sit there for a minute or so.
-
Sorry, I should have been more clear. The most helpful information from those will be at the very end where a summary is posted. It will look like this:
--- cs82.wac.edgecastcdn.net ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 9.307/10.876/12.445/1.569 msCan you do that once more please?
-
LOL. As you can see, I didn’t quite get the idea. I thought it was in a loop so I terminated the process. So that’s what the “100” is: a loop limit.
Here you go: ping -c 100 leisureguy.wordpress.com
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 37.395/52.908/300.125/33.167 msAnd: ping -c 100 s1.wp.com
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.980/28.111/62.746/5.682 ms -
BTW, the problem, though still occurring intermittently, seems to happen a little less often. I did hit it once in Chrome, but I don’t do much on WordPress in Chrome. Still, it does continue to happen every several operations (e.g., Add New Post, save a post, etc.). s1.wp.com seems to be the primary villain currently.
-
Thanks so much for running those again! It is indeed a loop. :)
Just to be sure, have you cleared your cache and cookies in Chrome recently? And are you using the homepage editor or the classic editor, since it seems like most of the issues you reference are related to the editing experience?
-
I do use the classic editor rather than the beep-beep-boop editor, since I greatly prefer the look and feel of the classic editor. Is that likely to be the source of the problem?
I’ll try clearing cache and cookies from my Chrome browser and rerunning the tests.
Okay, I cleared cache and cookies for the past week. Now the test:
ping -c 100 leisureguy.wordpress.com
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 30.308/37.785/265.642/23.675 msping -c 100 s1.wp.com
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 23.410/30.776/137.506/17.758 msBTW, I really dislike the beep-beep-boop editor and go the circuitous route through dashboard to be able to use the classic editor. Is the classic editor to be discontinued?
-
Just now, in classic editor sitting at a post just blogged. I click “Add new” and wait for 1 min 10 sec while “connecting to s1.wp.com” shows on the screen, then screen clears and I wait 20 seconds for “connecting to s2.wp.com”.
As you might expect, this does interrupt blogging flow and train of thought. When I click “Add new” I have something in mind to write, and the wait is intolerable.
A parallel: the phone company discovered that the amount of time people would wait for a dial tone before becoming annoyed at the delay was 1/10th second. Once they complete dialing and wait for the ringing to start, a delay of up to 15 seconds was acceptable (and delays now tend to be longer: with AT&T U-verse, a wait of 20 seconds before the ring starts is not unusual).
The reason is obvious: in dialing, one has a number in mind and a task to do and the wait is an interruption. After the number is entered, the task is completed, and a wait is more tolerable (and is probably used constructively, to mentally review purpose of call, how to approach it, etc.).
-
Thanks so much for doing that again. And for the additional workflow information. That does sound totally frustrating and derailing.
I’m going to ask our systems team to take a look, but I’ll need a little bit more technical information from you. Can you please follow the steps here to get your traceroutes and HTTP headers for me?
-
Here it is:
traceroute: Warning: leisureguy.wordpress.com has multiple addresses; using 192.0.78.13
traceroute to lb.wordpress.com (192.0.78.13), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 5.119 ms 1.180 ms 1.101 ms
2 107-205-200-2.lightspeed.mtryca.sbcglobal.net (107.205.200.2) 19.566 ms 19.275 ms 19.483 ms
3 * * *
4 99.134.39.25 (99.134.39.25) 20.532 ms 21.881 ms 19.563 ms
5 12.83.47.137 (12.83.47.137) 21.315 ms
12.83.47.129 (12.83.47.129) 45.804 ms
12.83.47.137 (12.83.47.137) 23.167 ms
6 gar23.sffca.ip.att.net (12.122.114.5) 23.956 ms 26.594 ms 23.688 ms
7 * 192.205.32.210 (192.205.32.210) 29.038 ms 25.637 ms
8 * * ae-3-80.edge2.losangeles9.level3.net (4.69.144.143) 35.239 ms
9 * * ae-2-70.edge2.losangeles9.level3.net (4.69.144.79) 35.030 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *And at that point, it gave me a command prompt.
-
Thank you! I’ve asked our developers to take a look and I’ll get back to you as soon as I hear from them.
-
This morning an endless wait on s1.wp.com, not on my blog, but on a regular site that I was trying to see in Chrome. Here’s the URL if you want to try:
- The topic ‘How can I shorten the wait times.’ is closed to new replies.
WordPress.com Forums 