Comments on: Perceived Speed Performace http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/ I design compelling experiences and create stunning photography. Thu, 15 Dec 2011 23:09:37 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: rudraksha http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-1603 rudraksha Sat, 05 Mar 2011 11:05:01 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-1603 It isn’t just about JavaScript performance though, the battle for the hearts and minds is perceived It isn’t just about JavaScript performance though, the battle for the hearts and minds is perceived

]]> By: Identifying the problem requires understanding what correlation is (and what it isn’t) « the philosopher developer http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-1557 Identifying the problem requires understanding what correlation is (and what it isn’t) « the philosopher developer Wed, 02 Feb 2011 22:35:51 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-1557 [...] phenomenon: copying files in Windows Vista is faster than in Windows XP but feels slower; Google Chrome appears to load up much faster than Mozilla Firefox, even though Firefox is nearly as ...; and so on. So I cannot claim that my boss was “wrong” for wanting to revert back to [...] [...] phenomenon: copying files in Windows Vista is faster than in Windows XP but feels slower; Google Chrome appears to load up much faster than Mozilla Firefox, even though Firefox is nearly as …; and so on. So I cannot claim that my boss was “wrong” for wanting to revert back to [...]

]]> By: Rob http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-1023 Rob Sat, 18 Dec 2010 04:45:23 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-1023 hi John, interesting article! You write “in Chrome the title is not shown un- til the website has completed loading”. I don’t see this (Chrome 5) at all. Tried several different pages. The page title appears in the tab after page rendering has started but not after the whole page being ready. On this same subject, you also write “This is a simple trick that allows Chrome to feel faster in that once the title is shown, the page is ready.” Do you have data to back this up, that this makes Chrome feel faster? Without data it’s a hypothesis and I would very much like to see this one tested/validated. As a web performance consultant, I´m very interested in perceived performance. Keep up the good work, Rob hi John,

interesting article!

You write “in Chrome the title is not shown un- til the website has completed loading”.
I don’t see this (Chrome 5) at all. Tried several different pages.
The page title appears in the tab after page rendering has started but not after the whole page being ready.

On this same subject, you also write “This is a simple trick that allows Chrome to feel faster in that once the title is shown, the page is ready.”
Do you have data to back this up, that this makes Chrome feel faster? Without data it’s a hypothesis and I would very much like to see this one tested/validated. As a web performance consultant, I´m very interested in perceived performance.

Keep up the good work,
Rob

]]> By: Firefox 4 startup gets faster | All my RSS http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-560 Firefox 4 startup gets faster | All my RSS Sun, 19 Sep 2010 14:32:51 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-560 [...] for quite a while. Over the summer, a pair of Mozilla interns looked at simple tweaks which would make Firefox appear faster. It now looks as if at least one of the suggested changes will make its way in to Firefox 4. [...] [...] for quite a while. Over the summer, a pair of Mozilla interns looked at simple tweaks which would make Firefox appear faster. It now looks as if at least one of the suggested changes will make its way in to Firefox 4. [...]

]]> By: Studying perceived performance of Firefox and Chrome http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-238 Studying perceived performance of Firefox and Chrome Fri, 16 Jul 2010 20:23:46 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-238 [...] It isn’t just about JavaScript performance though, the battle for the hearts and minds is perceived performance. This is a tough game for Mozilla as the average user giving Chrome a shot is doing so on a fresh [...] [...] It isn’t just about JavaScript performance though, the battle for the hearts and minds is perceived performance. This is a tough game for Mozilla as the average user giving Chrome a shot is doing so on a fresh [...]

]]> By: It's just plain wrong http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-210 It's just plain wrong Wed, 14 Jul 2010 08:00:03 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-210 First of all, "Firefox was loaded with at least four tabs" and "Chrome was only loaded with one tab" - whose fault is this? Instead of writing the entire article, recording YouTube videos and drawing several charts, you could have rather done the experiment the right way and displayed a single chart. This way the whole experiment has no value. Second thing, the "Window done drawing time" is clearly enormous in Firefox compared to Chrome. This has nothing with perception, it's a measured value. Firefox with no extensions takes several seconds to even show in taskbar on a cold start, while Chrome is started instantly each time! Since this *is* an open-source application with numerous developers working on it, it would be much wiser to concentrate on delaying a bunch of secondary stuff (which is obviously secondary, since Chrome manages to avoid it) and bringing the content as fast as possible. Chrome does use more memory however, but having 4Gb RAM is practically the lower limit these days. I still can't believe Firefox has become one of the slower brosers around! Google for "browser speed comparison", and you will find that FF3.6. is usually *the* slowest browser of all. First of all, “Firefox was loaded with at least four tabs” and “Chrome was only loaded with one tab” – whose fault is this? Instead of writing the entire article, recording YouTube videos and drawing several charts, you could have rather done the experiment the right way and displayed a single chart. This way the whole experiment has no value.

Second thing, the “Window done drawing time” is clearly enormous in Firefox compared to Chrome. This has nothing with perception, it’s a measured value. Firefox with no extensions takes several seconds to even show in taskbar on a cold start, while Chrome is started instantly each time!

Since this *is* an open-source application with numerous developers working on it, it would be much wiser to concentrate on delaying a bunch of secondary stuff (which is obviously secondary, since Chrome manages to avoid it) and bringing the content as fast as possible. Chrome does use more memory however, but having 4Gb RAM is practically the lower limit these days.

I still can’t believe Firefox has become one of the slower brosers around! Google for “browser speed comparison”, and you will find that FF3.6. is usually *the* slowest browser of all.

]]> By: Manuel http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-144 Manuel Mon, 28 Jun 2010 14:59:43 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-144 On my system (Intel Atom 330 + Intel SSD, so not-so-fast CPU but very-fast storage), fresh installs, Firefox takes some seconds to start (the Windows cursor shows the system is loading the application) while Chrome starts instantly. I also tried to disable the update-on-startup feature, but nothing changed. On my system (Intel Atom 330 + Intel SSD, so not-so-fast CPU but very-fast storage), fresh installs, Firefox takes some seconds to start (the Windows cursor shows the system is loading the application) while Chrome starts instantly. I also tried to disable the update-on-startup feature, but nothing changed.

]]> By: Morten http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-136 Morten Sun, 27 Jun 2010 16:07:46 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-136 Firefox is slow. No doubt about it. All benchmark tests point to this. Everything else are fanboys talking. Firefox is slow. No doubt about it. All benchmark tests point to this. Everything else are fanboys talking.

]]> By: Estudando a performace do Firefox e Chrome | Web Absolute http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-118 Estudando a performace do Firefox e Chrome | Web Absolute Wed, 23 Jun 2010 15:52:50 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-118 [...] sobre o desempenho de JavaScript, no entanto, a batalha pelos corações e mentes é percebida no desempenho feito por John Wayne. Este é um jogo difícil para o Mozilla como o usuário médio, o Chrome é um navegador novo, sem [...] [...] sobre o desempenho de JavaScript, no entanto, a batalha pelos corações e mentes é percebida no desempenho feito por John Wayne. Este é um jogo difícil para o Mozilla como o usuário médio, o Chrome é um navegador novo, sem [...]

]]> By: Bob http://www.johnwaynehill.com/blog/2010/06/16/perceived-speed-performace/comment-page-1/#comment-116 Bob Wed, 23 Jun 2010 10:22:22 +0000 http://www.johnwaynehill.com/blog/?p=128#comment-116 Perhaps history and bookmarks could be loaded in the background. That would make firefox feel faster. Perhaps history and bookmarks could be loaded in the background. That would make firefox feel faster.

]]>