<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
 
    <title>JavaScript Rules - google</title>
    <link href="http://javascriptrules.com/tag/google.xml" rel="self"/>
    <link href="http://javascriptrules.com"/>
    <updated>2013-03-10T17:19:20-07:00</updated>
    <id>http://javascriptrules.com/tag/google</id>
    <author>
        <name>Marcel Duran</name>
        <email>marcelduran@gmail.com</email>
    </author>
 
    
    
    
    <entry>
        <title>Web Metrics Framework</title>
        <link href="http://javascriptrules.com/2010/08/25/web-metrics-framework"/>
        <updated>2010-08-25T00:00:00-07:00</updated>
        <id>/2010/08/25/web-metrics-framework</id>
        <content type="html">&lt;p&gt;Recently &lt;a href='http://code.google.com/speed/articles/web-metrics.html'&gt;Google Web Metrics&lt;/a&gt; report came across and inspired by my co-worker Stoyan Stefanov&amp;#8217;s &lt;a href='http://www.phpied.com/wtf/'&gt;WTF - Web Testing Framework&lt;/a&gt; I decided to build my own ruleset for &lt;a href='http://developer.yahoo.com/yslow/'&gt;YSlow&lt;/a&gt; using these metrics to check how good or bad pages are compared to Top and All Sites averages.&lt;/p&gt;

&lt;p&gt;Last edition of &lt;a href='http://en.oreilly.com/velocity2010'&gt;O&amp;#8217;Reilly Velocity Conference&lt;/a&gt;, Stoyan demonstrated &lt;a href='http://en.oreilly.com/velocity2010/public/schedule/detail/15306'&gt;how easy is to build your own YSlow ruleset&lt;/a&gt; and following his &lt;a href='http://www.phpied.com/wtf/'&gt;post&lt;/a&gt; and &lt;a href='http://github.com/stoyan/Web-Testing-Framework/'&gt;source code&lt;/a&gt; I was able to make it. This first release of this &lt;a href='http://labs.javascriptrules.com/wmf/'&gt;extension&lt;/a&gt; of &lt;a href='http://developer.yahoo.com/yslow/'&gt;extension&lt;/a&gt; of &lt;a href='http://getfirebug.com/'&gt;extension&lt;/a&gt; features:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Google Web Metrics from 2010-05-26&lt;/li&gt;

&lt;li&gt;Top and All Sites metrics rulesets&lt;/li&gt;

&lt;li&gt;Use percentile to score when available&lt;/li&gt;

&lt;li&gt;Use SSH metrics for HTTPS pages&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;img src='http://javascriptrules.com/images/wmf.png' alt='Screenshot: Web Metrics Framework for YSlow for Firebug for Firefox' /&gt;&lt;/p&gt;

&lt;h3 id='gimme'&gt;Gimme!&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;The code is &lt;a href='http://github.com/marcelduran/Web-Metrics-Framework'&gt;in GitHub&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;Install it from &lt;a href='https://addons.mozilla.org/en-US/firefox/addon/221495/'&gt;Mozilla Addon Page&lt;/a&gt; or &lt;a href='http://labs.javascriptrules.com/wmf/download/'&gt;Download Page&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id='usage'&gt;Usage&lt;/h3&gt;

&lt;p&gt;After installing this extension you will see 2 new rulesets in the YSlow rulesets drop down list:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Web Metrics Framework - Top Sites&lt;/li&gt;

&lt;li&gt;Web Metrics Framework - All Sites&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Choose one of these rulesets and click &lt;strong&gt;Run Test&lt;/strong&gt; button. The current page will be evaluated using the Google web metrics data.&lt;/p&gt;

&lt;h3 id='metrics'&gt;Metrics&lt;/h3&gt;

&lt;p&gt;The metrics provided by Google on its article are mainly averages with some percentiles and SSL data. YSlow rules need a lint function that evaluates an input returning a score from 0 to 100 which is later used to give the F to A score system using weights.&lt;br /&gt;Since not all metrics have percentiles I had to compare the page metrics with the average multiplied by a magic number (4) to create a range from 0 to 4 * average (if any statistic savvy here has comments on it please help me out to find a better way to evaluate) which is good enough to have an outcome where being in the average deserves a C. Perhaps Google releases new reports in future updates with all metrics percentiles, this extension could benefit from those numbers and become more accurate.&lt;br /&gt;If the page being checked is secure (HTTPS), the SSL data available on the report is used instead. The weighting distribution was given by:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Every metric starts with 1&lt;/li&gt;

&lt;li&gt;Metrics with percentile get 1 more&lt;/li&gt;

&lt;li&gt;Metrics directly related to wire traffic payload or number of requests also get 1 more&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Again: statistics savvy, help me improving this extension with your valuable feedback&lt;/em&gt;&lt;/p&gt;

&lt;h3 id='conclusion'&gt;Conclusion&lt;/h3&gt;

&lt;p&gt;Although these metrics aren&amp;#8217;t 100% accurate (see &lt;a href='http://code.google.com/speed/articles/web-metrics.html'&gt;&lt;strong&gt;Caveats section&lt;/strong&gt;&lt;/a&gt; on Google&amp;#8217;s article) it&amp;#8217;s a good resource to compare your site with a sample of several billion pages crawled by Googlebot. Have fun!&lt;/p&gt;

&lt;p&gt;WARNING: Like &lt;a href='http://jslint.com/'&gt;JSLint&lt;/a&gt;, Web Metrics Framework might hurt your feelings :-)&lt;/p&gt;

&lt;p&gt;DISCLAIMER: This extension is not related with Google Inc. or Yahoo! Inc.&lt;/p&gt;</content>
    </entry>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
 
</feed>
