Introducing Page Speed
googlewebmastercentral.blogspot.com
Introducing Page Speed
1–10 of 21 posts
Re: Introducing Page Speed
#2I look forward to seeing some comparisons of this to YSlow
Re: Introducing Page Speed
#3I just tried this. It has a lot of overlap with YSlow, but there are some interesting extra rules in it, most notably a rule that finds inefficient CSS selectors. That's kind of cool.
Re: Introducing Page Speed
#4You may also want to try this: http://www.webpagetest.org/test
Pretty charts, and pretty good diagnostic.
(Health warning: knowing how much junk is spewing down the wire from some sites may turn your stomach ...)
Re: Introducing Page Speed
#5I look forward to seeing some comparisons of this to YSlow
Seems to have some overlap as mentioned in other comments - buy why the need to compare the two? Why not just add both to your toolbox and gain the features of both?
Re: Introducing Page Speed
#6Was I the only person who was a little surprised that they didn't mention YSlow by name? That strikes me as somewhat rude, though I know Yahoo and Google aren't exactly best buddies.
Edit: Looks like some of the commenters there agree with me on that point.
Re: Introducing Page Speed
#7I just tried this. It has a lot of overlap with YSlow, but there are some interesting extra rules in it, most notably a rule that finds inefficient CSS selectors. That's kind of cool.
These tools (like YSlow) are oh so interesting when your clients install them in their browser and examine the site you built for them. Now, I'll get to hear complaints that we used too many inefficient CSS selectors (and that we're incompetent), ignoring the fact that a .0003 millisecond makes no difference to the client's website. It's not Google's fault, but I just had to sigh when I saw some of the rules (I'll expect a call by tomorrow haha). :-)
Re: Introducing Page Speed
#8I just tried this. It has a lot of overlap with YSlow, but there are some interesting extra rules in it, most notably a rule that finds inefficient CSS selectors. That's kind of cool.
These tools (like YSlow) are oh so interesting when your clients install them in their browser and examine the site you built for them. Now, I'll get to hear complaints that we used too many inefficient CSS selectors (and that we're incompetent), ignoring the fact that a .0003 millisecond makes no difference to the client's website. It's not Google's fault, but I just had to sigh when I saw some of the rules (I'll ex…
I could actually see it working in the other direction. Things like YSlow highlight good technique in a (seemingly) objective way.
As for your issue, I would hope that if a client is savvy enough to check with these tools, they could also understand when you tell them what is important and what is not.
Re: Introducing Page Speed
#9I just tried this. It has a lot of overlap with YSlow, but there are some interesting extra rules in it, most notably a rule that finds inefficient CSS selectors. That's kind of cool.
The best thing I liked about PageSpeed as against YSlow is that it provides very specific action items. Very novice website owners can also follow the instructions.
A good addition would be the Printable Version of the report the way YSlow provides.
On Page Speed Activity tab, it seemed to be all messed up. It did the activity profiling for all pages open currently in the browser and not only for the specific page open in the current tab. Bug ? or did I miss some settings.
Re: Introducing Page Speed
#10Wouldn't it be interesting if Google started applying a bias to search results, pushing fast sites up the list?
I would definitely appreciate that option. I hate slow web sites.