Caching and Backup Plugins are a Pain

Feb 10th 2020

Ever find yourself having to deal with problems related to your backups and/or caching plugins? Find that perhaps they are contributing to bloat on your WordPress site? Don’t use them! Relying on your hosting provider is a way better solution and here’s why...

Caching via WordPress can be a bad idea

The reason is that each web request that comes in needs to first pass through some load balancers, then make its way to the web server which will then probably handoff the request to your PHP application server running WordPress. That’s a lot of steps that can be circumvented easily.

Not to mention that your PHP application needs start executing some PHP script to figure out what cached file to return.

When dealing with cache, it’s better to have a cached response at the web server level, this way, the request doesn’t get passed to the PHP application and no PHP code needs to be executed. Usually your hosting provider will provide this through a CDN or some other caching technology. WidePath does this seamlessly with a CDN (content delivery network) – so you don’t even need to think about it.

Same for backups, they are literally eating your CPU and bandwidth resources because they need to run via PHP. It is maybe possible that your backup plugin stores backups locally in which case your bandwidth is not being used – but backups should not be stored locally otherwise what is the point!

Your hosting provider, and WidePath is no exception here too, can tap into your data in a faster way, using a private network so your bandwidth and CPU remain untouched.

If you don’t have a hosting provider that offers these features, then give WidePath a try. We’re currently offering a promotion of 5 free sites, that’s plenty to get started and try us out.