shift8

Hello!

Thanks for the kind words 🙂

We definitely appreciate any feedback like this as it can always help us improve our services most definitely.

This type of thing however is a bit difficult to diagnose as (I’m sure you can appreciate) there are a ton of factors that may have a part to play in the measurement of site user experience that your performing.

I’ll answer your questions below, and I have a few questions of my own in some of the answers :

(1) I haven’t waited long enough?

The CDN performs a fetch from the geographic endpoint thats nearest to the person requesting the resource.

So if someone from Germany requests your theme’s style.css, the German CDN endpoint will fetch (And subsequently cache for future requests) that file.

If someone from Texas makes the same request, the same thing has to happen. So think of the fetching-then-caching action as dependent on where you are in the world. This is how most CDNs work.

(2) Shift8CDN isn’t the fast CDN that i need?

This is a tough one to answer. There are a few parts of the world that don’t have as good coverage (geographically) as places like Europe, North America and (most) of Asia. For example, China isn’t the greatest because of data exchange costs being a bit too high to justify. We have many other great Asian endpoints.

How are you measuring how fast the CDN is? Are you testing the speed of a specific static element (i.e. a single image file served through the CDN) , or are you measuring the overall site speed when our CDN is enabled?

I just need some specific references of “not fast enough” so I can go ahead and measure. IF you dont mind sharing your site URL as well as what country you are in , that would be helpful for me to test our CDN endpoints nearest to you.

(3) CDN is just not right for my website?

I think generally CDNs are great for any site. The only time it might not make sense is if your site is so minimal and compact (i.e not media heavy and very minimal theme with little to no jQuery), it might not be as needed.

Lets get an idea of what your site URL is and where in the world your located and I can try to run some tests on my side so I can see we are dealing with. Also if you dont mind sharing how your actually testing, that would be helpful too.

If you are willing to spend a bit of time , it would be definitely appreciated because anything I do find I hope to make the service a bit better maybe!

Thanks again 🙂

Thank you for the kind words! Tell your friends! 🙂

Thank you for the feedback, I did document the instructions on my original blog post that (hopefully) brought you here in the first place.

I will say that a 1-star review will hurt more than help, but its obviously your prerogative to give that rating for a plugin that is open source and so new that at this early stage, more constructive feedback would be more helpful than a 1-star review.

I will publish more concise documentation on the plugin Readme. Thank you again for the suggestion.

Closing this issue but feel free to reach out if its still happening!

Thank you kind sir!

Hello!

Great question. The CDN indeed fetches a copy of the media and stores it locally in memory and in a cache file structured folder.

I would say that its not the most ideal scenario to just delete the source because depending on the age of the media, browser caching and as well CDN caching settings based on the media file type, it may still need to refresh the media or check if it has changed for future requests.

The idea of the CDN (and CDNs in general) is to offload the number of requests and network latency, not remove the source outright.

You should still have the source image available in this case for ours and most other CDNs.

Thanks!

Hello!

Our plugin doesnt save any data for the website. What the wordpress plugin does do is rewrite all static asset URLs (i.e. media , css ,etc) to go through our CDN url.

IF you have deactivated and uninstalled our plugin and those URLs are still present on your website, what is most likely happening is you have a caching plugin that has cached our rewrites. I would recommend ensuring all caches are cleared and the plugin is truly deactivated and uninstalled and also do a browser cache clear and check again.

If it still persists I would need more info , perhaps the debug info from the plugin support tab or more info about your site.

Thank you!