External profiling tools might help too, but isolating the bottleneck is the most obvious approach to find the issue, as other things going on can contribute and cause something else to appear like being the bottleneck. I experienced a couple bugs before that won’t relate to the app but the browser API or possibly driver related that can temporarily appear, especially when a shader bomb dropped.