Help with profiling webGL

Hi guys,

I'm trying to look at my webGL content in a systematic way to see where there are bottlenecks & potential low hanging improvements. I'm going to post more but my initial question is, neither myself nor a developer can profile the GPU in webGL whilst it's connected to a browser with the content running. Nothing shows up in the GPU window.

Is this a limitation?

If so, does profiling within the Editor give you a pretty good idea of what the GPU is doing?

What's the benefit to profiling the content directly?

Thanks,
T