WebPagetest Forums

Full Version: CDN not detected after switching to https
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi there,

I have an issue with two of my websites. I switched them to https today and now MaxCDN is not recognized by the webpagetest anymore.

I talked to the support from MaxCDN, they are friendly and helpful, all settings are correct (I use WordPress and W3 Total Cache, latest versions each). They cannot explain why Webpagetest.org doesn't recognize the CDN.

I was wondering if anyone around here had an idea that could help me to fix this. I don't think the results will have a positive or negative impact on SEO (please correct me if I am wrong), but I would like to understand what is going on and see the much better results I used to have again (almost everything used to be an A).

If someone is interested, the according domains are https://www.taniaflores.com and https://www.ceho.de (please delete them from the post if it's not appropriate to the URL's them here).

Any help is appreciated. Thanks a lot!
Do you have a link to the test results? That will help track down the issue.
Yes, I just made new ones for you. Unfortuntaly I do not haver older ones to compare.



Thank you very much!
You sure it's actually running on the CDN configuration?

Resolving the IP for http://www.taniaflores.com from the east and west coasts in the US I get as the IP address (which also reverse-lookups to taniaflores.com). That alone wouldn't necessarily say anything since MaxCDN uses an anycast network but the traceroutes from both the east and west coast of the US seem to be routing to Europe.

West coast:

traceroute to (, 30 hops max, 60 byte packets
1 ( 1.920 ms 1.895 ms 1.890 ms
2 int-0-1-0-3.r1.pao1.isc.org ( 0.928 ms 0.943 ms 0.976 ms
3 palo-b1-link.telia.net ( 0.482 ms 0.504 ms 0.503 ms
4 sjo-b21-link.telia.net ( 1.479 ms las-b21-link.telia.net ( 14.954 ms sjo-b21-link.telia.net ( 1.492 ms
5 ash-bb3-link.telia.net ( 73.925 ms nyk-bb1-link.telia.net ( 73.863 ms sjo-b21-link.telia.net ( 16.457 ms
6 ash-bb3-link.telia.net ( 87.608 ms hbg-bb1-link.telia.net ( 174.203 ms 174.041 ms
7 bei-b1-link.telia.net ( 162.357 ms bei-b1-link.telia.net ( 180.881 ms bei-b1-link.telia.net ( 167.567 ms
8 xe-1-3-0.core-b30.as6724.net ( 163.036 ms 163.198 ms 163.177 ms
9 ae1.0.core-b30.as6724.net ( 158.134 ms 163.408 ms 158.005 ms
10 vl443.dcata-b9.as6724.net ( 158.027 ms 158.056 ms ae11.0.core-b2.as6724.net ( 177.170 ms
11 vl443.dcata-b9.as6724.net ( 177.051 ms taniaflores.com ( 163.829 ms vl443.dcata-b9.as6724.net ( 177.115 ms

East Coast:

1 lo0-100.WASHDC-VFTTP-326.verizon-gni.net ( 4.171 ms 4.169 ms 4.159 ms
2 T1-1-0-11.WASHDC-LCR-22.verizon-gni.net ( 6.686 ms 6.697 ms 6.691 ms
3 so-14-0-0-0.RES-BB-RTR2.verizon-gni.net ( 24.002 ms ae24-0.RES-BB-RTR2.verizon-gni.net ( 4.248 ms *
4 * * *
5 0.ae9.GW11.IAD8.ALTER.NET ( 6.642 ms 0.ae1.GW11.IAD8.ALTER.NET ( 6.684 ms 0.ae4.GW11.IAD8.ALTER.NET ( 6.602 ms
6 teliasonera-gw.customer.alter.net ( 8.881 ms 6.446 ms 6.433 ms
7 ash-bb3-link.telia.net ( 6.380 ms ash-bb3-link.telia.net ( 6.366 ms ash-bb3-link.telia.net ( 6.262 ms
8 hbg-bb1-link.telia.net ( 103.822 ms hbg-bb1-link.telia.net ( 98.744 ms hbg-bb1-link.telia.net ( 103.805 ms
9 bei-b1-link.telia.net ( 106.474 ms bei-b1-link.telia.net ( 106.410 ms 106.356 ms
10 xe-1-3-0.core-b30.as6724.net ( 106.368 ms 103.659 ms 106.344 ms
11 ae11.0.core-b2.as6724.net ( 106.332 ms 105.031 ms ae1.0.core-b30.as6724.net ( 103.091 ms
12 vl443.dcata-b9.as6724.net ( 115.083 ms 112.671 ms vl425.dcata-b9.as6724.net ( 107.412 ms
13 taniaflores.com ( 107.359 ms 109.982 ms 112.063 ms

There also aren't any of the normal CDN headers (which also isn't conclusive by itself).

Are you sure the sites are actually configured and running on the CDN?
Yes, I am quite sure. You can check on pages like pingdom


or with Google Page Speed and you will see that all files are served from the CDN.

And like I said, the support staff from MaxCDN actually confirmed the settings should be correct. Nevertheless there seems to be an issue, otherwise the CDN would still be recognized correctly after switching from http to https, am I right?
I think the problem is that the Firefox tests you ran weren't showing the resources coming from the CDN (possibly because they are SPDY which isn't currently reported for Firefox or IE). If you test in Chrome you can see the requests and CDN detection correctly: http://www.webpagetest.org/result/150724...a9a6eabfa/
Hi Patrick, thank you very much, that information helps me a lot.
Reference URL's