Well, that depends. When you are getting the fields from the “custom blocks” this creates additional queries for every post object that needs to be retrieved. So there will be a performance hit. The more queries the bigger the performance loss.
I have a site where I did the same thing, I called the blocks “panels” and created a post type for “global panels” the idea what that when content needed to be duplicated, and only when content needed to be duplicated, then the client would use a global panel. But things got out of hand. Rather than create layouts in the page they created them all using the globals and then just picked the ones they want. So it turns out they could copy one global panel and then create a test page to show it, then when they were ready to make it live they could go to the page that it was supposed to be on and swap out the old one for the new one. So now the site has nothing but “global panels”. This has created a query nightmare. A good caching plugin with aggressive caching rules solves most of the performance issues this has created.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
ACF PRO’s Flexible Content field allows you to create smaller pieces of UI and compose them into whole flexible patterns. In our latest article, we show how to use it to create swappable site sections and integrate it all in a theme.https://t.co/ZRocH8oJSp— Advanced Custom Fields (@wp_acf) January 24, 2023
© 2023 Advanced Custom Fields.