Pardon me if this has been mentionned before but I just solved an issue I've had literraly for months and couldn't find the answer anywhere.
My game is running perfectly fine on my Win7 workstation and was just horrible on a Win7 laptop with intel HD graphics 3000.
Seems like Scirra was still searching for an answer: https://www.bountysource.com/issues/2781707-terrible-performance-in-node-webkit-0-10-rc1?utm_campaign=plugin&utm_content=tracker%2F51989&utm_medium=issues&utm_source=github Ashley
This helped me: https://github.com/rogerwang/node-webkit/issues/185 but I still had the issue with the previous Node-Webkit release.
I've seen lots of threads where people encounter this issue. And all kinds of suggested solutions that didn't work as far as defragging your harddrive...
Here's how I solved it.
I just downloaded the latest Node-Webkit version release today (22 July 2014)
Here it is http://dl.node-webkit.org/v0.10.0/node-webkit-v0.10.0-win-ia32.zip (from: https://github.com/rogerwang/node-webkit)
Add your package.nw file to the new node-webkit files, rename the nw.exe to your game name.
(The name you get when the project is exported to node-webkit)
And finally, move these two files in the same folder than all the rest of the files.
"d3dcompiler_43.dll" & "D3DX9_43.dll"
You will find the first file in the installer of Chrome, and you should already have the last one somewhere on your computer. I found mine in an Adobe folder. If not, just search it on google.
You should finally be able to run your game at full speed.
This was tricky since the "renderer" expression used in a text object would tell you tha tit's using WebGL but it was in fact disabled as all object with effects would be left unaffected.
I hope Scirra will be able to find a way to integrate this in later releases.