Firefox (Chrome and Safari) support are really high on the list of things to get done but it's a rewrite of a good chunk of pagetest (along with some browser-specific code) so I haven't started yet. It'll probably be the next "big" change I work on after I get some plumbing changes done.

I am not sure if this has been mentioned before but it kind of ties in with your idea of comparing tests from the test history.

The test history page is pretty much a big list of tests everyone has submitted. For users who chose to register, you could have another tab, or even a search filter on the test history page. This would allow users to see only tests they have submitted.

Logged in users should be able to delete their own test results as well if you do this so the information can remain neat and organized.

I've been planning on doing that but it just hasn't bubbled up. The user information is stored with each test in the history so filtering for your tests would be trivial to implement (may do it today if I get a few cycles).

Deleting your own tests would be a little bit harder. The history is stored in flat files right now so removing things from them isn't pretty. If/when I put a database store behind them it will become a lot easier (been trying to avoid a database for simplicity on the stand-alone deployments but I should be able to make it optional).

The test history page will now default to showing you only your tests (if you are logged in) and there is a checkbox that you can check to see everybody's (non-private anyway). You should be able to see your own private tests when you look at the history.

I was looking at the video and realized that there is one cool way to improve decision making there and you already have all the information - I'm talking about combining screenshot video with waterfall diagram!

Basically, screenshot videos show rendering progress and waterfalls show download progress and it makes a lot of sense to show them side by side to hint on which downloads actually important and which are not and so on.

How I see the result is simply having screen shots on the top and waterfall on the bottom, waterfall slowly revealing the timeline (you can just crop the waterfall to appropriate time point).

I've got a pretty good idea what you're thinking about as it's something that has been asked before internally, I just haven't had time to do it because it requires some fairly involved drawing code that would manually draw all of the video frames for the waterfall (and have to figure out how to make the waterfall readable in a video).

Are you thinking the full waterfall, with just the line items revealed and some form of "you are here" indicator or just the "active" requests at any point in time (could end up being quite a few though).

Anyway, I think the main goal is to help people make connection with stuff being downloaded and displayed or not displayed more importantly. I think the best lesson for people might be that stuff might need to be downloaded later because it's not used yet, although it's hard to say until I see the results.

Connection is not direct, of course, as stuff takes time to render, there are multiple dependencies and all that, but some conclusions can still be made.

Now, thinking about all this, I think it makes sense to show connection diagram instead of a waterfall - there are much fewer connections (although quite a few anyway) and they stay open for the duration of the page load (once open) and their "continuity" is sort-of "relevant" to video process.

I know, this is hardly specific request, but that's all I can say without seeing something - it's hard to say what will work and what will not here.