YSlow 2.0 and ShowSlow 0.2 with updated beacon

ShowSlow logo

Just a few days ago I wrote first version of ShowSlow and then released it Open Source.

But progress is unstoppable and Yahoo! released long-awaited YSlow 2.0 so it’s time for ShowSlow 0.2.

This means that I’m sitting down and analyzing Beacon parameters to make sure ShowSlow can collect data properly – so here’s the list of parameters that YSlow 2.0 is sending with the beacon (actual set of y* parameters depends on the profile used – ydefault sends them all):

Once again, to configure YSlow to send your data to a beacon, you need to set a couple configuration parameters on about:config page of your browser:

for YSlow 1.x

  • extensions.firebug.yslow.beaconUrl = http://www.showslow.com/beacon/yslow/
  • extensions.firebug.yslow.optinBeacon = true

for YSlow 2.x

  • extensions.firebug.yslow.beaconUrl = http://www.showslow.com/beacon/yslow/
  • extensions.firebug.yslow.optinBeacon = true

Where beacon URL is either public: http://www.showslow.com/beacon/yslow/ (your measurements will be shown to public so please make sure you’re OK with it before you use it) or private URL on your instance which you can get here: http://code.google.com/p/showslow/source/checkout.

ShowSlow

ShowSlow logo

OK, ShowSlow is taking shape and I decided to follow “Release Early, Release Often” motto so now it’s open source: http://code.google.com/p/showslow/

Current version accepts YSlow beacons and you can configure your browser to post to public showslow.com beacon or install your own instance if, for example, you want to hide the results from others.

Sample screenshot (amazon.com):
Sample Screenshot (amazon.com)

New York Web Performance Meetup

After talking to Steve Souders about local events at Web2.0Expo in San Francisco, I realized that New York is missing Web Performance optimization event. I went ahead and saved 75% using Meetup.com discount code (Web2SF09 – graciously provided by Derek Odegard of Meetup team) and now you’re welcome to join New York Web Performance Workshop meetup.

Our first even is planned for May 12 and I’m looking for location at the moment, talking to a few companies I had preliminary OK from. In the first part of the event, we’re going to talk about current state of tools for web performance analysis and optimization and in the second part we’re going to look at the real-life sites and what can be done to improve their performance.

Performance @ New York Web Standards Meetup

The New York Web Standards MeetupYesterday, I talked about Web Performance at New York Web Standards Meetup hosted by theMechanism.

Thanks to all attendees for coming to the presentation, I hope it was informative and worked as a call to action.

If you have any questions or need help with your performance optimization project, feel free to post your comments here or contact me directly if you want, I’ll be happy to help.

HTML Slides with meta-data embedded using RDFa are available here

If you’d like to watch more presentations on performance (already have about 30 of them), you can visit TechPresentations: http://www.techpresentations.org/Performance

Including a couple presentations about YSlow and related tools: http://www.techpresentations.org/YSlow

Once again, thank to all attending, asking interesting questions and volunteering for YSlow treatment ;)

Sergey

TypePad Connect and rel=”canonical”

Some time ago I created MediaWiki Widget for TypePad Connect:
http://www.mediawikiwidgets.org/TypePad_Connect

While editing a wiki page and going to different versions of it, I noticed that Comments widget has a well known issue – it has no idea which comments should be displayed on the page if page has different URLs (ad campaign tracking codes will probably be a main commercial issue, but also editing interfaces in MediaWiki and other CMS softwares and so on) – you can see example of what I’m talking about on these two pages:

which represent the same content page with different URL.

Other frameworks like JS-Kit, for example, solve this problem by allowing to pass URL or ID of the page to the widget, but I just had an idea about new approach to this issue.

The thing is that Google, Yahoo! and Microsoft just announced a new tag in order to fight SEO spam (and I already installed MW extension from Wikia):

<link rel="canonical" href="http://www.mediawikiwidgets.org/TypePad_Connect"/>

The idea is very simple – they just need to know all the pages that legitimately think that they are copies of page X so their smart algorithm that fights page duplication spam will have more clues.

But the side effect is that tools like TypePad Connect or JS-Kit can automatically, on the fly identify the pages they should serve content for. All you need to do is to write a simple jQuery code like this (my first line of jQuery) :

var canonical = $('html:first > head:first > link[rel=canonical]').attr('href');

I think all of us will benefit if widgetized tool providers like TypePad will push for this as solution to the page identity problems.

I hope this will be included into a list of high priority issues and TypePad Connect will get improved first (I actually enjoyed creating widget for it – it was much-much easier then with other vendors).