too much Minimal impact on memory usage ?

Hi @banijadev !

We will look into this but so far, the memory impact here is mostly because of the blocks added in the Block Editor. That is what contributed to the memory usage. In the frontend, it’s not affected.

We’ll continue to investigate this ??

Hey @banijadev we’ve been adding performance improvements and we were able to shave off some memory usage as you can see here: https://wphive.com/plugins/stackable-ultimate-gutenberg-blocks/?plugin_version=3.11.0

It may still show an ? but this is because of how memory scoring is computed in WPHive.. whether a plugin is memory friendly or not is computed against all the other plugins in the Plugin Directory, and because I would assume that the vast majority of plugins are smaller plugins, then Stackable’s score gets skewed to showing as being not friendly. Most of our memory overhead is introduced because of registering blocks inside Gutenberg.

I’m marking this thread as resolved. But rest assured, we will be continuing to make things more memory efficient.