they are already cached by user browsers, so this shouldn't impact.
One for the programmers
I believe he was talking about the actual custom js that sits in the html.
We are aware of this but it really isn't an issue or something of high priorty.
We'll get to it eventually.
Thanks Cybrax!
Glad to be of some use Jon, there are days I get sick of looking at my own code lol! so it's a refreshing change for me.
not sure if this is related but if I keep chess.com tab open in Firefox (v9.0 and older) by the end of the day it will use about 2Gb of RAM and I have to restart the browser since slow down my laptop. It is not related to the new redesign since it happened in the old version as well. any idea how to solve it?
If you need help, please contact our Help and Support team.
Here's one for the programmers (as I've been picking holes with the design) so they don't feel left out..
Is there any reason why the Google analytics, Meebo, Quantserve & several other small blocks of javascripts cannot be moved from inside the page HTML to external .js files where they can be cached by the users browser? (same applies to the feeback form/ tab if that is become a permanant feature)
I know it's only a small reduction in the page size but given the high volume of traffic such changes should result in some savings of the daily outgoing bandwidth consumption from the webserver(s).