Webdev:Cesium:Beacons: Difference between revisions

← Older edit

Webdev:Cesium:Beacons (view source)

Revision as of 05:06, 12 August 2009

1,241 bytes added , 12 August 2009

→‎YSlow 2.0.1

Rdoherty

975

edits

@@ Line 1: / Line 1: @@
-= Overview<br>  =
+= Overview =
 This page is for tracking beacon information from YSlow and PageSpeed. It is intended both as a reference '''and''' brainstorming tool.<br>
-<br>
+= YSlow&nbsp;Beacon Parameters =
-= YSlow&nbsp;Beacon Parameters<br>  =
 *w – size of the page in bytes (v1 sent size in kilobytes)
@@ Line 38: / Line 36: @@
 *ynofilter – Avoid AlphaImageLoader filter
 *yimgnoscale – Do not scale images in HTML
-*yfavicon – Make favicon small and cacheable<br>
+*yfavicon – Make favicon small and cacheable
+= PageSpeed Beacon Parameters =
+Currently, Page Speed does not support beacons, but starting v1.2 it will, [[#PageSpeed 1.2|see more info below]].
-<br>
+= Future Beacon Parameters =
-= PageSpeed Beacon Parameters<br>  =
+A future goal is to have YSlow and PageSpeed beacon detailed information about a page's performance. This can be in addition to a normal GET request. The URL parameters can have basic information while a larger response in the POST body can contain detailed statistics regarding a page's assets and score.
-TBD.
+=== YSlow 2.0.1 ===
+Starting with v2.0.1, besides the existing beacon preference: beaconUrl and optinBeacon, a new preference will be added to control the information to be included in the beacon.
-[http://code.google.com/p/page-speed/issues/detail?id=58 http://code.google.com/p/page-speed/issues/detail?id=58]<br>
+Preference Name: beaconInfo
+Possible values: "basic", "all", "grade", "stats", "comps" or a comma separated list of "grade", "stats" and "comps".
-<br>
+Default value of the preference is basic. The YSlow beacon will be sent with HTTP GET. This is for backward compatibility.
-= Future Beacon Parameters&nbsp;<br>  =
+For all other values, the beacon will be sent by HTTP POST.
-A future goal is to have YSlow and PageSpeed beacon detailed information about a page's performance. This can be in addition to a normal GET&nbsp;request. The URL&nbsp;parameters can have basic information while a larger response in the POST&nbsp;body can contain detailed statistics regarding a page's assets and score.
+New beacon parameters:
+* lt - Page load time (basic)
+* g - json tree of the resultset (scores of all rules in the ruleset) (grade)
+* w_c - page weight with primed cache (stats)
+* r_c - number of requests with primed cache (stats)
+* stats - json tree of stats, e.g. <pre>{"doc": { "r": 1, "w": 36.1 }, "js": {"r": 3, "w": 29.0 }</pre> (stats)
+* stats_c - json tree of stats with primed cache (stats)
+* comps - json tree of comps, e.g. <pre>{"doc": { "url": url, "w": size, "gzip": 36.1, "cr": 320, "cs": 971,"expires": "2009/10/11", "response": 537, "etag": "xxx-xx"}}</pre> (comps)
-=== YSlow<br>  ===
+[[Webdev:Cesium:Beacon:YSlow_2.0.1|Example beacon]]
-*Number of JS&nbsp;files
+=== PageSpeed 1.2 ===
-*Number of CSS&nbsp;files
-*Number of images
-*Total size of components (HTML, JS, CSS, Images)
-*Cached/uncached page weight
-*Components that do not meet rules
-**URL&nbsp;
-**Criteria
-=== PageSpeed  ===
+Starting with v1.2, Google PageSpeed will start supporting beacons. You can see documentation in progress here: [http://code.google.com/p/page-speed/wiki/BeaconDocs http://code.google.com/p/page-speed/wiki/BeaconDocs]
-TBD.
+And original bug used for tracking this feature here: [http://code.google.com/p/page-speed/issues/detail?id=58 http://code.google.com/p/page-speed/issues/detail?id=58]