Caching is a concept that every website should have in place

[hasan018542]

I’ll switch analogies momentarily to try to explain this more clearly. When remodeling a house, you paint the rooms first before redoing the floors. If you redid the floors first and then painted the rooms, the new floors would get paint on them and you’d have to go back and tend to the floors again later. When a browser loads a webpage, it goes through a process called (coincidentally) “painting.” Each page is “painted” as the browser receives bits of data from the webpage’s source code.


This painting process can either be executed efficiently (i.e. painting walls before qatar gambling data refinishing floors), or it can be done in a more chaotic out-of-order fashion that requires several trips back to the beginning of the process to redo or fix or add something that could’ve/should’ve been done earlier in the process. WebPageTest.org Test Result (Filmstrip View) Image source: WebPageTest.org Test Result (Filmstrip View) Here’s where things can get technical, but it’s important to do whatever you can to help your site drive the “track” more efficiently.


to make loading a webpage easier on the browser. It already takes long enough for a browser to process all of a page’s source code and paint it out visually to the user, so you might as well have that source code ready to go on the server. By default, without caching, that’s not the case. Without caching, the website’s CMS and the server can still be working on generating the webpage’s source code while the browser is waiting to paint the page.


This can cause the browser to have to pause and wait for more code to come from the server. With caching, the source code of a page is pre-compiled on the server so that it’s totally ready to be sent to the browser in full in one shot. Think of it like a photocopier having plenty of copies of a document already produced and ready to be handed out, instead of making a copy on demand each time someone asks for one.