Hi there, @baziday,
I’m sorry to hear about the trouble, but thanks for reaching out.
I checked your site and I see we’re in a good place to start investigating your problem: the site redirects the http URL to the https URL, and the Jetpack connection loos nice and healthy.
If you have multiple URL versions of your site in place (HTTP, HTTPS, and more – I can see them pointing to the main URL https://junkyardsocialclub.org/ which is expected behaviour), it’s normal that the debugger detects them all.
I can also confirm that the primary Jetpack connection is established with a different WordPress.com account. Can you try connecting Jetpack again using your WordPress.com account (which has the same username) and see how it goes? We have some instructions here to orientate yourself.
Let me know how you get on.
Hello Stef, Thank you for your reply. This is my client’s account. The reason I’m asking is that we are troubleshooting a long TTFB. I’d like to disconnect completely from jetpack to see if that improves site loading time. Just now, I have disconnected JetPack. Could you please disconnect if from the wordpress.com account (and anywhere else). That way I can run the test again and see if it made any difference. Thank you so much!
Hey @baziday,
Sure thing, no problem. I have disconnected your client’s account from the site, which was already disconnected form Jetpack with no token existing.
You should be able to run your tests now 🙂
Let me know how it goes and if you get stuck at any step, just let us know and we’ll be glad to help.
Hey @baziday,
Do you have updates about that? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!
