I ran some tests with a stopwatch.
(I start the timer when I hit the preview button in C2 and stop it when I see the game running).
NW.js - 10.5 - took about 4 to 5 seconds to see the loading bar and another 40 seconds of loading. Total ~ 45 seconds
Firefox - most of the time did not even show a loading bar and sometimes brought up a script dialog box. Overall times were around 21 to 35 seconds depending on what it was in the mood for. Total ~ 21 to 35 seconds
Chrome - slightly faster than NW at about 3 to 4 seconds to bring up the load bar, and maybe 30 seconds to load. Total ~ 34 seconds
Note: I usually close the game before running a new preview, because it only saved a couple seconds leaving it running.
NW.js - 10.5 very smooth 60fps and very low cpu usage around 2%
Firefox very unpredictable loading, but fine afterwords, pretty smooth 60fps and slightly higher cpu usage around 11%
Chrome smooth at windowed size, but garbage fps when maximized, cpu usage around 6%
Game type: Isometric with pre-rendered 3d animations. Uses pathfinding and mouse click movement (like Age of Empires or Baldur's Gate)
Stats: (shown either at status bar at bottom of project or in-game)
approx download: 26.8
memory use 146 (around 113 in game)
object count (in game): 196
very minimal particle effects
very minimal webgl effects
Note: I have not yet created any audio for this game yet. It does feature quite a few detailed animations being that it is isometric and needs to have different directions animated. The levels are very small, and there will only be 2 or 4 characters on screen at most.
gtx 680 superclocked
standard 7200rpm hdd
win 7 pro