Pagespeed
My job requires analysis of each and every object on a website's page. Analysis down the details of parsing each and every header in HTTP response to figure what happened in the round trip of an object. Lately, i came across a tool, Firebug, that very nicely merges with Firefox. Firebug acts as a platform on top of which a lot of other tools can integrate. Pagespeed [from Google] & Yslow [from Yahoo] are couple of very famous ones which are now widely used by web developers.
These tools provide rules that analyze embedded objects and suggest actions that can make their delivery faster. Read here for more details on rule. Yslow provides almost the same rules. Based on how your page fares on these rules, a score is given to you. These rules contain everything that can make your content deliver faster and make end user experience richer.
With Akamai in picture, biggest problem i was facing was figuring out what object was treated in what way at our edge. We do have plugins like LiveHttpHeader to look at response headers but then with 120 objects on page, things go out of hands. I have modified Pagespeed's code in way that it shows all Akamai relevant information to me in the resource tab of pagespeed. On this page, i get to see what treatment an object got on our Server. Which server the request went to ? And how many tiers did the request involve. Thanks to Pagespeed brilliantly written infrastructure, these changes were not very hard to plan and implement. To know more, contact me :)
0 Comments:
Post a Comment
<< Home