Have you tried using the debug layout feature in construct2 to see what it is that is using up most of you cpu?
The layout size can't be changed at runtime and it actually wouldn't have any effect I think. If your graphics are the issue causing the framedrop your focus should be on reducing the size of them.
If your background is made up of one picture, at 1200x1920 it's at least using 9MB of memory and if it's placed in a power of two texture (I don't know if cocoonjs still does that for every texture) even 16MB.
But Graphics are not the only thing capable of reducing framerate, so finding out what is should be your first concern.