New website broken on Chrome browser
View Single Post
Join Date: Dec 2007
01-13-2012, 12:26 AM
Originally Posted by
The problem is you put new resources at the old location and so the browsers still had the old resources cached. There is a way to prevent this problem 100% of the time so there are no issues. If you change an image, css, js or any other resource file give it a new url that you have not used before.
What I suggest is putting a version number in a url and setting it to cache forever. That way your website always works for people, you never run into outdated cache versions and the pages run insanely faster.
I have taken some websites from 10 seconds load times to .5 seconds just doing this kind of stuff.
^ This. That's exactly what I just wrote above this post.