dawnbreak wrote:
I'm back with both barrels loaded

.......Shutting it down then turning it on again seems to have worked thank you
Why does that happen though?
The reason it happens is because some common content requests get cached by your browser. The reason for caching data is to reduce bandwidth demands and while also increasing the speed at which the browser can re-render the content. The cache simply stores common data which is called repeatedly locally on the machine which is obviously the quickest method of retrieval.
The problem comes when your local cache data goes out of sync with the physical content because the associated links to the content being served may no longer match 100%. Another cause would be the caching of corrupted data which means the association is good but your local data is bad rendering errors in the page.
The website also has a server side cache which can also become corrupted or out of sync. The website cache gets refreshed at a more frequent rate than a local cache which helps maintain its integrity. The server side cache also stores data based on client requests so if everyone is reading the same content repeatedly it will hold the highest priority in the cache which means the content is delivered faster and creates less demand on the server resources. Because people are viewing different things over time the cache data is in a constant state of flux resulting in more frequent refreshes. It's also set to clear periodically to make sure it's relatively fresh in the event that the client activity isn't creating enough demand to cause a change in the cache.
That's probably way too much information,