I have a hard time understanding how Asphalt 8, Modern Combat, Titan Quest etc. can all run on my device yet somehow a simple 2D game is maxing it out
3D games in particular have a very different rendering approach. Many GPUs have limited bandwidth, and the fact 3D games have depth allow them to use a front-to-back approach that more or less ensures every pixel is only drawn to once, at least for the basic color pass. Many Construct users naively create a stack of 14 force-own-texture layers, causing every pixel to be written to at least 14 times, which absolutely hammers the GPU bandwidth for all it's worth. Then traditionally they blame HTML5, Construct, browsers etc. without recognising what they've done.
Part of this is the game design aspect: AAA games are built by experts who know this GPU performance stuff inside-out. If you're an indie dev just starting out with Construct, things like fillrate limitations are often things you learn about the hard way.
I'd really like to recommend again that you use your own tool to make (and release/troubleshoot) a full sized platformer game (on at least Steam for Windows) and experience the issues that others like myself have reported here.
I do work with very large projects. Thanks to the developers sharing them, I do privately have C2 projects for games like Airscape and The Next Penelope. On the whole, they seemed to work fine, and the C2 engine was holding up great. The Next Penelope in particular had some issues with using too much fillrate early on, but Aurelien made some game design changes to reduce excessive layers, effects etc. and then it fit much better within GPU hardware limitations. That is exactly what I was talking about above. So my view here is not due to naivety, it's actually based on working with these very large projects.