Use data-heavy shortcodes efficiently
Queries, maps, galleries, video players and interactive collections cost more than simple editorial content. Configure the smallest useful result and test the complete page.
Query-backed elements
For Listings (Feed), calendars, favorites and taxonomy collections:
- choose the narrowest saved query or source;
- use a deliberate result limit;
- exclude the current item where appropriate;
- paginate long result sets;
- avoid repeating the same query in several components;
- use one reusable feed template for repeated cards.
When Faceted Search is enabled, keep every control and result area on the same context and expose only fields visitors genuinely need.
Media-heavy elements
- Select an appropriate WordPress image size.
- Avoid full-size images for small cards or thumbnails.
- Limit gallery, carousel and slider item counts.
- Use poster images and interaction-delayed video loading when available.
- Do not place several autoplaying media components on one page.
- Keep 360-image and scroll-sequence frame sets proportional to their visible size and purpose.
Maps and third-party embeds
Use one map with several markers instead of several maps when the visitor task allows it. External iframes, advertising, social feeds and map services add third-party requests; include them only where they provide direct value.
Nested components
Deeply nested rows and interactive components increase markup and make responsive behavior harder to maintain. Remove empty layout elements and avoid nesting a query-backed component inside every result card.
Measure the public page
- Test logged out.
- Check initial loading before interaction.
- Trigger sliders, maps, videos, filters and load-more controls.
- Check narrow viewports.
- Confirm the page remains usable on a slower connection.
- Remove components or options that do not improve the visitor task.