There are several things on my “to do” list for WebPagetest and I figured who better to help decide what is most important than the users. I can’t guarantee that I’ll work on things in the order voted because I’ll have to weigh it against what we need internally as well but it will strongly influence the direction.
Here’s the current list (roughly in the order I was going to work on them):
Compare multiple tests against each other: Initially by selecting multiple tests from the test history but eventually other ways to select the tests to compare. You’ll get a bunch of stacked bar charts for times, requests, bytes, etc. After the basics are done then interleaved waterfalls will also be attempted.
Zoom in on waterfall: At the top of the details page you’ll be able to “zoom” into the render, dom, doc complete or fully loaded times which will only show the requests that had activity during that time and will change the horizontal scale as well. Eventually it will also support an arbitrary min and max (which could also be useful for having a fixed time scale when looking at 2 different waterfalls). This should make it easier for getting useful waterfalls for presentations.
Simpler optimization results: On the main results page, instead of showing a thumbnail of the optimization checklist, display a simple table that indicates which checks did well and which didn’t (probably with a better indication of the “critical” and “less important” checks). The optimization checklist would also be grouped by “critical”, “important” and “nice to have”
Custom Headers and Cookies: The ability to specify custom http headers and cookies to be used for a test.
Commenting on tests: At a minimum, when submitting a test you’ll be able to add a note about what the test is for and it’ll show up in the history as well as when looking at the results. Not sure about letting comments be added after a test was run
Add more optimization checks: Incorporate more of the checks that YSlow and Page Speed do into pagetest.
Improve the documentation: The current wiki on sourceforge is pretty lame (and sourceforge locked it down when they stopped supporting wikis). This would cover documentation for pagetest, webpagetest, urlblast and the optimization checks