Not to be negative, but I don't know if the benchmarks tell you much given the fact that Servo still has a ways to go before it renders sites properly.
I periodically test it out (most recently yesterday, in fact) and on popular sites like espn.com and cnn.com it doesn't render them properly. Meaning, not the padding is a little off, but parts of the page simply don't render at all.
This is not a criticism of their efforts, which are impressive, just pointing out that it might not be ready to compare in terms of performance.
You are generally correct, and this is why we don't often publish numbers.
However we have made an effort to implement things we expect will have an effect on our performance first to counteract this.
There are also sites included in our page load suite that Servo renders quite well, and should be a fair comparison.
Another reason benchmarks are hard is that many of Servo's individual pieces are blazing fast, and we do many tasks in parallel, but end-to-end performance still needs work and tuning, which is why our initial page load numbers are below Firefox. This is in large part due to the community concentrating on those hard parts and not spending any time on things like the network stack or disk caching.
A key point is that there is so much low hanging fruit that it is falling off the tree by accident (as seen in the suffix list PR). New contributors can make a huge impact here with minimal effort.
I periodically test it out (most recently yesterday, in fact) and on popular sites like espn.com and cnn.com it doesn't render them properly. Meaning, not the padding is a little off, but parts of the page simply don't render at all.
This is not a criticism of their efforts, which are impressive, just pointing out that it might not be ready to compare in terms of performance.