>Could it be the browser rather than the server?

maybe... but it's more likely to be a function of what's going on with your cache. I see this more often on a busier system.

http://home.mn.rr.com/wwftd/