Nice idea but poorly implemented

Coming from a free Cloudflare account which did not require a plugin, I assumed KeyCDN would be a smoother more integrated experience given this dedicated plugin.

Quite the opposite. Went through the KeyCDN setup process, plugin installed, Cache Enabler installed. All checks done. And more than 50% of the images are not being served by the CDN. The plugin does not recognise or fix this.

I don’t know if the issue is directly the plugin or the CDN. But the fact ther plugin is there to control things, if it doesn’t recognise that most of the images are not being served by the CDN, then what is the point of it?

Sales support was there, tech support seems to be non-existent. Troubleshooting is a combination of convoluted or not-applicable (it even states if using this plugin, relative domains won’t work, yet the plugin has an option for that). None of my images were relative domains anyway.

The only reason for KeyCDN over cloudflare was the cookie-free domain issue. But if it doesn’t even deal with the basics of ensuring all images are served from the CDN, then what is the point?

Finally moving to KeyCDN and this plugin was just a big waste of time.

• This topic was modified 6 years, 6 months ago by mikejd30.