Block Registration: Improve Frontend Performance

[n7studios]

Summary

This update refines how Gutenberg blocks are registered by detecting whether register_block_type() is running on the frontend or within an admin/editor context.

When the call occurs on the frontend, we now skip loading editor-only block properties. These properties are not required for frontend rendering and can trigger unnecessary resource refresh operations (forms, landing pages, products), which may be contributing to the elevated 401 Unauthorized errors noted here: https://linear.app/kit/issue/WP-48/wordpress-investigate-high-count-of-401-unauthorized-errors.

By avoiding these unnecessary initialisations, we reduce API calls and lower memory usage.

Before:

After:

Testing

Existing tests pass.

Checklist

• I have written a test and included it in this PR
• I have run all tests and they pass
• The code passes when running the PHP CodeSniffer
• Code meets WordPress Coding Standards for PHP, HTML, CSS and JS
• Security and Sanitization requirements have been followed
• I have assigned a reviewer or two to review this PR (if you're not sure who to assign, we can do this step for you)

[github-actions]

WordPress Playground

🚀 Your PR has been built and is ready for testing in WordPress Playground!

Click here to test your changes in WordPress Playground