Ashley has a point, investing to a young technology which has potential to improve in time. But currently, within this decade, I'm with digitalsoapbox on this one, HTML5 is too young, javascript so slow... Even making a small Flappy Bird game is far more stable making in Unity for an Android Jellybean phone from 2012 than making on C2.
As far as I remember, my tests back then has a performance of 60fps stable no significant spike for the game made on Unity and 24fps unstable, frequent lag spikes and unplayable for the one made on Construct 2.
Theoretical FPSs or hypothetical speeds between native and html5 doesn't matter anymore when real life benchmarks are so significantly bad.
In conclusion: Ashley you're so wrong ...