Safari Leaves Chrome and Firefox in the Dust
blog.animatron.com
Safari Leaves Chrome and Firefox in the Dust
1–8 of 8 posts
Re: Safari Leaves Chrome and Firefox in the Dust
#2Accurate title: our Safari users have faster load times than Chrome or Firefox users.
And the author's theory that they're wealthier, have better access to high-speed internet, and/or have newer machines is probably enough to explain it.
Re: Safari Leaves Chrome and Firefox in the Dust
#3cage match: Safari and Chrome!
Re: Safari Leaves Chrome and Firefox in the Dust
#4Accurate title: our Safari users have faster load times than Chrome or Firefox users. And the author's theory that they're wealthier, have better access to high-speed internet, and/or have newer machines is probably enough to explain it.
I could not actually find any such differences when doing segmentation by geo location. So I don't think that's enough to explain it.
Re: Safari Leaves Chrome and Firefox in the Dust
#5Fail fail fail
Safari doesn't support navigation timing api, you are not comparing apples with apples, just showing off the failings in your analytics provider.
Re: Safari Leaves Chrome and Firefox in the Dust
#6Fail fail fail Safari doesn't support navigation timing api, you are not comparing apples with apples, just showing off the failings in your analytics provider.
The navigation timing API seems to work in Safari 8 (Yosemite).
Re: Safari Leaves Chrome and Firefox in the Dust
#7Fail fail fail Safari doesn't support navigation timing api, you are not comparing apples with apples, just showing off the failings in your analytics provider.
hmm, it seems to work just fine. why do you think it is not supported?
Re: Safari Leaves Chrome and Firefox in the Dust
#8Fail fail fail Safari doesn't support navigation timing api, you are not comparing apples with apples, just showing off the failings in your analytics provider.
hmm, it seems to work just fine. why do you think it is not supported?
safari 8 supports it: http://caniuse.com/#feat=nav-timing