Once “Disable cache” is deselected, open up a web page, keeping the Developer Tools open to the Network tab. It could be any page – even this one. The Network panel will show all of the loaded assets on the page you loaded. This will include the images, the JavaScripts, the stylesheets, and even the underlying HTML of the page itself. You will see a lot of information for each of the downloaded items. One of the Network Panel columns is “Size” which, as you probably can guess, shows how big the downloaded item is. If you don’t see “Size” in your list, you can right-click on the headers for the list of downloads and customize the columns to show.
image 2 -
Customizing the columns shown in the Network panel.
Now, there is an exception to the size of the file being shown new zealand whatsapp number data 5 million in this column. This happens when a file wasn’t accessed through the Network at all but, instead, through the browser’s cache. The browser will cache some items on your computer’s disk and some items in memory.
image 3 - Why Aren’t Clients Seeing the Changes I Made?
Examples of Size in the Network Panel.
If you look at the time taken to load elements you will notice that the disk cache is generally much faster than accessing items through the network and the memory cache is faster still. This is great for performance. This is not so great when a client wants to review the changes made to the stylesheet on their site, though.
Do you still have the Network Panel open? If so, you can view the difference that “shift reloading” makes. While holding down the Shift key on your keyboard, click the browser’s reload button. Most of the same assets that came from the disk or memory cache will now show their file size because the shift reload tells the browser to get a fresh copy of all of these files. This allows the user to see any changes made, and helps get development back on track.