Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter csandreas1

    (@csandreas1)

    Also why are the blocking metrics so much?

    • This reply was modified 6 years, 3 months ago by csandreas1.
    Anonymous User 3392934

    (@anonymized-3392934)

    Hey there, @csandreas1!

    Thank you for reaching out to us about Jetpack’s CDN, and I always appreciate the need for speed!

    Jetpack’s CDN relies on the WordPress.com infrastructure, which includes servers throughout the world. Although we do not currently have a public map of all server locations, Jetpack is geographically near many WordPress.com VIP locations:

    https://vip.files.wordpress.com/2017/12/distribution_map2x.png

    Although we have a location in Africa, it’s unlikely that is the location serving images to you. You can run this command in Terminal (or similar) to see which WordPress.com datacenter is serving you:

    curl -IsL wordpress.com| egrep "(HTTP|Location|X-ac)"

    For example, the output of the above command for me is:

    `
    HTTP/1.1 301 Moved Permanently
    Location: https://wordpress.com/
    X-ac: 1.ord
    HTTP/2 200
    `

    We use airport codes for locations; ORD is a data center near O’Hare. I’m located in Chicago, so this makes sense.

    When you initially use Jetpack’s CDN, the initial load will likely be slower. The first load of an image loads it into our CDN, where it is cached for an extended period. Since the image is cached, subsequent loads are significantly faster.

    If you were running a series of back-to-back speed tests in different regions, it’s likely our CDN didn’t cache the image across all regions yet. You may notice faster results on a re-test.

    It’s also possible that the origin server (your site) is closer to you than our nearest CDN; in that case, it is not surprising that images may load faster without the CDN enabled.

    Please let us know if you’ve had a chance to re-test, we’ll be happy to take another look! ??

    Anonymous User 3392934

    (@anonymized-3392934)

    Hey there again, @csandreas1!

    I wanted to provide you with more details on our CDN locations, so I checked in with our Systems team.

    We have more details on our server locations, here:

    https://www.peeringdb.com/asn/2635

    We also have a live map. You can hover over an area on the map to see what data centers are serving it:

    https://ac-map.automattic.com/?s=photon

    The locations are color-coded and update constantly. This also means the above webpage may “stutter” a bit when you move the mouse around.

    Please let us know if Jetpack’s CDN is consistently slower for you. Our Systems team would be happy to take a closer look at this. ??

    • This reply was modified 6 years, 3 months ago by Anonymous User 3392934. Reason: Photon → Jetpack CDN
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Jetpack images global CDN, makes images slower for me’ is closed to new replies.