Us: 752.05ms Chrome: 272.09ms

Need to profile where the time is spent. Is it js, or html parser, or DOM or layout.

Need to look at more closely what the test is actually timing, but at least the first profile showed almost all the time spent in layout, creating frames and reflowing. Setting innerHTML/parsing was like <5% of the total cpu time.

Hmm, back to DOM. If I read the testing code correctly, it is actually testing the sync innerHTML performance, not async framecreation.

Hmm, or not. If I make the test to do innerHTML on display:none element, we run the test 10x faster.

Whether or not the test is testing the right thing [1], reflow is too slow here. [1] https://github.com/robohornet/robohornet/issues/66

AFAIK, robohornet is not a thing anymore (if it ever was), and its tests are too broken to be useful. We can find better tests and profile those.