<b>Builder query loops can hide an N+1 problem</b>
Dynamic loops are convenient until your archive page makes 200 database queries.
— Each dynamic tag (post meta, ACF field, author avatar) inside a loop item can fire its own query per item.
— A 30-item grid pulling 5 custom fields each = 150 extra queries unless the builder batches them.
— Bricks and Elementor both let this happen; neither warns you.
<b>Pros:</b> dynamic loops kill the need for custom PHP templates.
<b>Cons:</b> uncached meta lookups multiply, TTFB climbs, object cache becomes mandatory.
Profile with Query Monitor before shipping any dynamic archive.
<b>Best for:</b> dynamic loops on sites with persistent object cache (Redis). Without one, hand-code heavy archives.
Builder Bench
@BuilderBench
<b>Builder query loops can hide an N+1 problem</b>
Этот пост опубликован в Telegram-канале Builder Bench. Подписаться можно по ссылке: @BuilderBench.