@Meenakshi YESSSSSSSSSSSSSSSS IT DOES OMG.
You browse the internet for both work and school, and site average being about 1/2 second slower then they need to be because of crappy programming, and negligence.
How many sites do you go to a day? 20, 50, 100? lets take the 50 number.
50 X .5 = 25 seconds. A day.
25 x 7 = 175 a week.
175/60 = ~ 3 minutes give or take.
3 * 12 = 36 minutes a year.
Again, is it the end of the world? No. But why should the web be a bloated piece of crap when local applications are almost instant?
Jeff is right, the web can be much better. If you have a decently fast computer, and chrome, you can SEE when the server side is horribly unoptimized and bloated. Its obvious, and users do appreciate it. Why, because the problem is MAGNIFIED if the user machine is NOT fast. If they are on a work terminal with a single core p4 and a gig of ram, in winxp, and your site doesnt even load on my 3 ghz dual core with 4 gb ram, what do you think is gonna happen if they have client side rendering lag? It ADDITIVE. Web developers need to understand how important this is. Its beyond just niche power user stuff here, its a HUGE market share of people without the latest and greatest hardware, that think your site sucks.