Hi Guys,
I’d like to use the page speed score as displayed on the results page of WPT for some internal reporting. I have WPTMonitor setup which downloads the API response on a regular basis.
The API responses contain the following info which I assume is the Page Speed data:-
<score_cache>48</score_cache>
<score_cdn>96</score_cdn>
<score_gzip>100</score_gzip>
<score_cookies>87</score_cookies>
<score_keep-alive>94</score_keep-alive>
<score_minify>91</score_minify>
<score_combine>75</score_combine>
<score_compress>99</score_compress>
<score_etags>93</score_etags>
What I’d like to know is…
Are the Page Speed results displayed on the results page of WPT for first view, repeat view or some sort of average of both?
What percentage do the A,B,C,D,E,F scores represent? (i.e. is B 80-90 and C 70-80??)
How is the overall score calculated? It isn’t included in the API so is the a formula I can use to produce it?
Great product btw
Thanks,
Giles
Sorry, I probably haven’t communicated the different optimization checks well enough. Right now there are actually 2 completely different sets of checks that are done by WebPagetest. The grades (and scores in the XML) come from proprietary checks that pre-date the Page Speed addition. I’m working with the Page Speed team to make sure they include everything that WebPagetest was checking and then I’m going to phase out the proprietary checks and migrate to using the Page Speed equivalents.
The scores that are displayed at the top of the main results page are for the median first-view test (and there should be a section in the XML that includes the information for the median run).
The grades are old-school increments of 10:
90-100 A
80-89 B
70-79 C
60-69 D
< 60 F
The overall score comes from Page Speed and is just a straight average of the individual checks done by Page Speed. I don’t expose the individual components right now but you can get the overall page speed score by including &pagespeed=1 in the xmlresult call (you may have to call xmlresult.php?test=… instead of the friendly url though). I have it disabled by default for right now because loading the page speed results can sometimes be very time consuming on the server side.
Thanks,
-Pat