Reasons Why Your Website Is Still Slow With A CDN | TechTree.com

Reasons Why Your Website Is Still Slow With A CDN

Content Delivery Networks is used to accelerate the web page load time thereby saving time.

 

Wondering why it takes so long to load a web page? You might want to check on a few details to ensure easy and smooth surfing.
Insufficient hardware resources
CDN offloads traffic from your web server, however your server hardware may still not be able to keep up even with the lightened web traffic. If you are still seeing CPU and RAM usage spikes, you might need to add or upgrade your hardware resources.
Software bugs or configuration faults can also cause CPU spikes and memory leaks. 
Make sure you have the latest OS and software patches on your server and check to see if all your server configurations are correct.
Network issues
Although a CDN is supposed to provide a more reliable and efficient network, the networking issues with your server's ISP could be causing a bandwidth bottleneck. Occasional outages on the Internet can also cause delays even if you have a CDN such as submarine communications cable accidentally being severed, natural disasters, thieves stealing fiber optic cables, DDoS attacks, and ISP routing issues and hardware outages.
Third party objects
Nowadays, sites are getting more and more bloated with objects hosted by third party, such as third party java scripts, analytic tools, and multi-media for time or cost saving reasons. CDNs are designed to accelerate or cache content coming from your server, but not objects hosted on third party servers. If a CDN were to cut down the delivery of objects from your site by 4 times, but third party objects make up 40 per cent of total page load time, you might only see 1.5 times improvement instead of 4. The higher percentage of total page load time third party objects take, the lower amount of CDN improvements will be noticed.
Improper cache settings
The more objects you can cache from your site, the higher the benefits you can receive from a CDN. Caching should not be taken lightly. Some objects should not be cached, such as html files and scripts that needs to be updated frequently. You can set lower cache-control ages for objects that needs to be updated frequently, but having low cache-control ages for static objects that do not change frequently will not optimize your CDN utilization. If you have a low traffic page you might require a longer cache-control age. If an object's cache-control age has expired, the next request will have to go back to the server instead of the CDN's edge.Watch out for conflicting Pragma headers. If you have a cache-control header to cache an object for a month, but you also have Pragma headers with "no-cache", your cache-control header setting might be overridden. This mistake might occur because of legacy settings or misconfigured CMS adding the Pragma headers by accident.


TAGS: Web Page, CPU, Content Delivery Networks

 
News Corner
IMP IMP IMP
##