Client Side Performance Thoughts

[bacoords]

Right now all the block settings are just dumped into JavaScript and dealt with there. I'm sure there's a more performant way to do this, including offloading some work onto the server ahead of time.

A list of random ideas open to discussion

• [ ] Rest API Endpoint and/or data store instead of wp_localize_script
• [ ] filtering and bundling of settings by block type on the server before load (would probably increase payload size, though)
• [ ] Stashing the registered settings in the object cache when WP_DEVELOPMENT_MODE is not set

[Lovor01]

I think at least first is fine. I always communicate with my code in block editor via extended REST endpoints. This would also mean that data will be sent only when requested which would speed up editor loading. Also, endpoint should be locked to only logged users. Splitting into per block settings would also enable granularly calling at expense of multiple requests which shouldn't be much of an issue for modern servers, but I think still less performant... I must think about this one