The Google Research blog also published some speed test results [googleresearch.blogspot.com], concluding with this killer observation:
|a daily impact of 0.5% is of real consequence at the scale of Google web search, or indeed at the scale of most Internet sites |
for me, one important issue that this research unconvered is that even delays under 0.5 second had a CUMULATIVE effect on the end user, deterring them from using the site as frequently.
Broadband made a lot of developers lazy - but as far as I'm concerned speed always was a secret weapon and it still is worth getting obsessive about.
Moderator Note: Google will be launching a new website devoted to website speed issues. The following post was moved here from another location:
|Webmasters looking for ways to speed up page loading times now have a host of tips and tricks to peruse as Google has launched a new website designed to emphasise the importance of speed on the web, said Richard Rabbat, a product manager at Google. |
...Google has already started to help web publishers test their sites for stragglers with a Firefox plug-in called PageSpeed, something that Yahoo! has also done with YSlow.
Link to article on CNET News below:
[edited by: tedster at 6:55 pm (utc) on June 25, 2009]
It looks like the core url for Google's speed intiative is [code.google.com...]
There's an introductory video where several Google engineers share the vision of a speedier future - and then the real goodies come from two links on the left:
There's really a treasure chest of information and tools here. I've only begun to explore it.
These videos started showing up on the webmaster YouTube channel a few days ago. Some basics, but some interesting topics.
I know what you mean - but sometimes I need a kick in the pants to remind me to get back to basics. This speed information has done just that for me.
I also noticed that Google's "Page Speed" plug-in for Firefox was just updated, too. I'll have to figure out what's new.
software developers should take notice. Many java calls default to being inside head area of cms's, which serves to slow down a browser BEFORE the bulk of the content loads up. Placing much of the extra calls in the footer would help the page slow down a browser AFTER the bulk is displayed... most won't even know there was a delay.
Once you know your software well you can optimize it a great deal but how many people bother? I'd like to see more emphasis placed on this at the software development stage instead of relying on the end user.
[edited by: JS_Harris at 10:56 am (utc) on June 27, 2009]
this is why i love google.
im ashamed to say that as a php developer i didnt know simple things like the difference between using double and single quotes for strings; the former looks for variables and replaces them with their value, the latter does not and thus uses less memory.
i havent come across a single book, tutorial or blog that pointed this out - thank you google.
Perl calls it interpolation. I don't recall ever seeing the term used in PHP but the online manual has always described the differences on the Strings [php.net] page.
But don't be ashamed, it is merely discovering/knowing your resources and you are correct, Google has provided yet another resource for us.