Title: High memory usage!?
Last modified: April 11, 2024

---

# High memory usage!?

 *  Resolved [najram](https://wordpress.org/support/users/najram/)
 * (@najram)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/high-memory-usage-11/)
 * Hi there,
 * this plugin looks quite promising … especially so in conjunction with its theme
   and for “gd-projects”.
 * However, a quick run through [plugintests.com](https://plugintests.com/plugins/wporg/blockstrap-page-builder-blocks/latest)
   reveals that it is quite heavy on memory usage for a block plugin – **6.75 MiB**.
   
   This is almost like the entire WooCommerce plugin …And in comparison with other
   quite powerful custom blocks plugins like e.g. GenerateBlocks, Greenshift or 
   Stackable ( respectively 128.69KiB, 386.38KiB and 754.99KiB ), the difference
   is huge.Is this just the way it is, or it can be improved in the future?
 * Also noticed the lack of the semantic html-tag choice for blocks, except for 
   heading block … at least the container block should also have it … at least, 
   in my opinion.
 * Cheers

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Stiofan](https://wordpress.org/support/users/stiofansisland/)
 * (@stiofansisland)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/high-memory-usage-11/#post-17680581)
 * Hi [@najram](https://wordpress.org/support/users/najram/),
 * Thanks for your questions, let me answer each point below:
    1. Memmory – We use our own system “Super Duper” which not only builds blocks for
       each feature but also makes it avaialable as a shortcode and a widget so that
       it as not only compatibility with the block builder but also most other page
       builders. The extra memmory useage comes from the fact that we extend the WP
       widget class and that is a memmory hog, but only in the backend. You can see
       these numbers are very small on the frontend.
    2. Woo – Woo is much more and also passes that onto the frontend unlike our plugin.
    3. Improvements – We plan to update our “Super Duper” class to work without extending
       the WP Widgets class, which will reduce the memory usage by 10x.
    4. html-tags – we are happy to listen to feedback on this. The reason we didn’t
       do this is becasue the plugin can be used with any theme and some themes already
       include them in palces we can’t repalce them so instead of duplicating them 
       we left them out.
 * In short, the memmory useage is only higher on the backend where it will not 
   affect the user. This is becasue of the WP Widgets class we extend. Memmory usage
   on the frontend is minimal.
 * Thanks,
 * Stiofan
 *  Thread Starter [najram](https://wordpress.org/support/users/najram/)
 * (@najram)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/high-memory-usage-11/#post-17696096)
 * Hi Stiofan,
 * Thank you for your reply.
 * Super Duper system is great. I really like, and it is actually very useful in
   your other plugins. In this one through, maybe not so much as it already is a
   blocks-only plugin … anyway, hope you’ll manage to update it soon.
 * With classic themes, you are quite right. With FSE on the other hand, the paradigm
   has changed. The task or responsibility to create the (almost)entire site’s structure
   is now on site creator’s shoulders. And, to be able to do it properly, quality
   tools are needed. There’s also no doubt about whether, nowadays, a semantic html-
   structure should be used or not in web development.
   So, as I see it, if you’re
   really serious about the “site/page builder blocks” part, then they should naturally
   include, not only html-tag selection option, but also additional custom attributes—
   sometimes css ids and classes are not enough.Nothing fancy is needed here. A 
   simple free-hand text input field for both, tag and additional attributes would
   get the job done — like the ones for id and additional classes … and of course,
   if left empty, defaults apply.
 * In my view, with just a bit of an extra effort on your part, implementing these
   two features, would make your plugin stand out of the crowd of “halfway” developed
   plugins, and actually a very useful tool for bootstrap-based website building.
 * Of course, the decision is yours, but I really hope you’ll go an extra mile with
   this.
 * Cheers 🙂

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘High memory usage!?’ is closed to new replies.

 * ![](https://ps.w.org/blockstrap-page-builder-blocks/assets/icon-256x256.jpg?rev
   =2922475)
 * [BlockStrap Page Builder - Bootstrap Blocks](https://wordpress.org/plugins/blockstrap-page-builder-blocks/)
 * [Support Threads](https://wordpress.org/support/plugin/blockstrap-page-builder-blocks/)
 * [Active Topics](https://wordpress.org/support/plugin/blockstrap-page-builder-blocks/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/blockstrap-page-builder-blocks/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/blockstrap-page-builder-blocks/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [najram](https://wordpress.org/support/users/najram/)
 * Last activity: [2 years, 1 month ago](https://wordpress.org/support/topic/high-memory-usage-11/#post-17696096)
 * Status: resolved