Average page loading time is increased too much
-
Hi, @ectra Thanks for your message and link to WP Hive.
Overall Maxi Blocks’ performance is the same or better compared to others. See our reasoning below.
Comparisons for reference
https://wphive.com/compare/plugins/maxi-blocks/vs/kadence-blocks/
https://wphive.com/compare/plugins/maxi-blocks/vs/stackable-ultimate-gutenberg-blocks/
What’s the real difference?
When you start digging deeper the increased load time on Maxi Blocks only applies in very specific cases on the admin side, not on the front-end visitor experience.
From an SEO performance perspective, Maxi Blocks is doing great.
Test our homepage as proof https://maxiblocks.com/ We get 100 on lighthouse metrics in Chrome dev tools. See the screenshots below.
The only time it loads slower if compared is when you create a new page /wp-admin/post-new.php in the editing experience. The reason is that we have many more block components (over 80) to load in the editor compared to others.
Just compare our template library and block patterns to others and you will see what we mean. The point is that this happens only once when you create a new page when it takes 3.7 seconds to load all the functionality. See the screenshots below.
This does not impact the visitor experience, or front-end SEO speed at all.
For some reason, wp-hive averages out the front end AND the back end which pushes up Maxi Blocks average page speed loading metrics when in fact it only applies to a specific case on the editing experience and not the front-end SEO speed. Please compare the metrics and it should be clear what we mean.
At the same time, we are currently working on optimisations to improve the initial load time in the editing experience for admins. We know how important speed is for everyone.
Check our demo library speed https://maxiblocks.com/demo/ – we know what it takes to make it fast.
Do you have any more questions? Happy to answer ??
- The topic ‘Average page loading time is increased too much’ is closed to new replies.
