It is suspected that the features viewer lags in some occasions, namely:
- When multiple nested sub-traces are defined
- When some traces are empty, which might lead to errors
- When big sequences are used as input, this might lead to an exploding number of calculations (especially with respect to the number of letters to be shown/hidden).
Test performance using Lighthouse 🚨 to have a quick overview.