Safari, at least version 5, seems to be too aggressive in firing the onload event. It seems to fire onload too early, even before done loading the HTML, leading to misleading page load time, particularly the t_page (I start this timer in a javascript snippet at the beginning of the page) tends to be misleadingly smaller than other browsers on small pages, and in some cases t_page is seen to be even 0.