Browser caching shows as failed for naked domain
|
10-03-2016, 09:54 PM
(This post was last modified: 10-03-2016 09:54 PM by HQRaja.)
Post: #5
|
|||
|
|||
RE: Browser caching shows as failed for naked domain
clubberz Wrote:That's strange, not sure why it doesn't display a cross or a tick for the html file now. Not sure either what might be causing that, as according to my knowledge, my server is configured to set the appropriate caching headers for all the files it serves. Though I'm gonna look into it again to make sure that really is the case. Thanks for the suggestion. clubberz Wrote:It does appear the CDN could potentially be slowing down the site so recommend doing some tests with and without it enabled to see if it's worth it. Thanks for recommending that. I just tried five tests with CDN and five without it, and here are the average results of some key metrics: Quote:CDN As you can see, using no CDN results in improved first view, while using one favors repeated views. Also, considering how the differences are marginal even when it comes to the first view, I think sticking with the CDN would be a good idea, because of the benefit of serving multiple geographical locations with similar results, and saving on the more expensive server bandwidth cost compared to the CDN bandwidth cost. Are there any further potential improvements you could suggest? |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Browser caching shows as failed for naked domain - HQRaja - 09-30-2016, 10:07 AM
RE: Browser caching shows as failed for naked domain - clubberz - 10-03-2016, 07:46 AM
RE: Browser caching shows as failed for naked domain - HQRaja - 10-03-2016, 07:54 AM
RE: Browser caching shows as failed for naked domain - clubberz - 10-03-2016, 12:12 PM
RE: Browser caching shows as failed for naked domain - HQRaja - 10-03-2016 09:54 PM
|
User(s) browsing this thread: 1 Guest(s)