Poor performance

Sorry to hear that! That definitely should not be happening.

Can you please use Jetpack’s Debugger module to send us some more information about your site?

1) Go to the Jetpack page in your dashboard.
2) Click on the Debug link appearing at the bottom of the page.
3) Click the link that says “click here to contact Jetpack support.”
4) Fill in the description box and your name and email address.
5) Click the “Contact Support” button.

Once we know more about your site and its configuration, we should be able to understand what’s slowing things down. Thanks!

Yes, the calls to wp.com were also my problem. I haven’t had the need to debug, you could see it all the time in the status bar of the browser (a lot of slow lookups).
Sorry, I do not want to install this again to debug, I used another fast plugin.

I can see directly that most of the hangups are calls to wp.com

the calls to wp.com were also my problem. I haven’t had the need to debug, you could see it all the time in the status bar of the browser (a lot of slow lookups).

Thank you both for the extra details. It seems you both have trouble accessing WordPress.com servers. We do have data centers all around the world, but if WordPress.com can’t be properly reached from where you live, we’d like to know! We do know for example that some WordPress.com resources are blocked in China. If you live in China, that may be what’s causing the issue.

If you’re willing to run some additional tests, it would be interesting to find out more about where the connection hangs, when running between your home connection and the closest Automattic data center. We can find that out by running a traceroute on your computer, as explained here. You could for example run a traceroute for dashboard.wordpress.com.

You can send me the results via this contact form and mention this thread in your email; I’ll be happy to take a look!

Thanks!

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\Steffen>ping dashboard.wordpress.com

Ping wird ausgeführt für dashboard.wordpress.com [192.0.78.13] mit 32 Bytes Daten:
Antwort von 192.0.78.13: Bytes=32 Zeit=23ms TTL=53
Antwort von 192.0.78.13: Bytes=32 Zeit=22ms TTL=53
Antwort von 192.0.78.13: Bytes=32 Zeit=22ms TTL=53
Antwort von 192.0.78.13: Bytes=32 Zeit=22ms TTL=53

Ping-Statistik für 192.0.78.13:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 22ms, Maximum = 23ms, Mittelwert = 22ms

C:\Users\Steffen>tracert dashboard.wordpress.com

Routenverfolgung zu dashboard.wordpress.com [192.0.78.13] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Zeitüberschreitung der Anforderung.
3 10 ms 9 ms 9 ms ip5886ba36.dynamic.kabel-deutschland.de [88.134.186.54]
4 14 ms 16 ms 14 ms ip5886bb24.dynamic.kabel-deutschland.de [88.134.187.36]
5 14 ms 15 ms 15 ms 88.134.202.82
6 13 ms 14 ms 12 ms 88.134.202.23
7 13 ms 20 ms 14 ms hbg-b1-link.telia.net [62.115.9.13]
8 13 ms 30 ms 20 ms 213.155.135.84
9 23 ms 23 ms 22 ms ffm-bb3-link.telia.net [62.115.112.46]
10 20 ms 19 ms 21 ms 62.115.121.5
11 34 ms 22 ms 22 ms automattic-ic-306957-ffm-b11.c.telia.net [62.115.46.38]
12 23 ms 23 ms 22 ms 192.0.78.13

Ablaufverfolgung beendet.

C:\Users\Steffen>ping wp.com

Ping wird ausgeführt für wp.com [192.0.78.25] mit 32 Bytes Daten:
Antwort von 192.0.78.25: Bytes=32 Zeit=25ms TTL=53
Antwort von 192.0.78.25: Bytes=32 Zeit=22ms TTL=53
Antwort von 192.0.78.25: Bytes=32 Zeit=22ms TTL=53
Antwort von 192.0.78.25: Bytes=32 Zeit=23ms TTL=53

Ping-Statistik für 192.0.78.25:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 22ms, Maximum = 25ms, Mittelwert = 23ms

C:\Users\Steffen>tracert wp.com

Routenverfolgung zu wp.com [192.0.78.25] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Zeitüberschreitung der Anforderung.
3 9 ms 9 ms 9 ms ip5886ba36.dynamic.kabel-deutschland.de [88.134.186.54]
4 14 ms 13 ms 14 ms ip5886bb24.dynamic.kabel-deutschland.de [88.134.187.36]
5 16 ms 15 ms 15 ms 88.134.202.78
6 12 ms 12 ms 12 ms 88.134.202.15
7 14 ms 14 ms 13 ms hbg-b1-link.telia.net [62.115.9.13]
8 15 ms 13 ms 13 ms 213.155.135.84
9 23 ms 22 ms 22 ms ffm-bb3-link.telia.net [62.115.112.42]
10 30 ms 19 ms 20 ms ffm-b1-link.telia.net [62.115.121.5]
11 22 ms 62 ms 22 ms automattic-ic-306957-ffm-b11.c.telia.net [62.115.46.38]
12 22 ms 22 ms 22 ms 192.0.78.25

Ablaufverfolgung beendet.

Thank you both! Those traceroutes don’t indicate any issues; dashboard.wordpress.com loads quickly.

Since you both mentioned seeing slow loading times for wp.com resources in your browser console, I wonder if you were both having trouble accessing a specific wp.com subdomain, while still being able to load dashboard.wordpress.com. If you ever give Jetpack another try, it would be interesting to know what resources seem to be the most problematic.

But of course, this is from MY machine, not the site’s, so what does it tell me? Nothing really.

@creative-i It will indeed only tell us about performance issues between your browser and WordPress.com, as you reported earlier. Do not hesitate to run the same tests from your site’s server if you have shell access. Let me know what you find!

It looks like your site can not communicate properly with Jetpack.

Could you click on the “click here to contact Jetpack support.” link, and use the contact form to send us your site’s debug results? They will tell us more about the connection issues between your site and WordPress.com.

Thanks!

Why can’t I just add the site stats?

Once you’ve enabled the plugin and connected it to WordPress.com, you’ll be able to deactivate all modules but the Stats, thus removing everything you don’t need. Once a module is deactivated, its code doesn’t run on your site. That should help!

• This reply was modified 8 years, 1 month ago by Jeremy Herve.

Please don’t post large blocks as you did above. They tend to get flagged as spam, and must wait for manual review. If you have large blocks of code to paste, use pastebin.com, gist.github.com, or wpbin.io and paste a link to that paste here.

@creative-i I have removed that log as it did contain some information you may not have wanted to share publicly on these forums.