Progressive archive loading
Progressive archive loading displays the archive structure first and loads result batches as the visitor reaches them. It is useful for long archives and taxonomy-split listings where rendering every card at once would delay the initial page.
When to use it
Consider progressive loading when:
- an archive contains many results;
- cards include large images or media;
- the archive is divided into several taxonomy sections;
- visitors normally browse rather than jump to a specific page number.
Use ordinary pagination when visitors need a stable numbered position, a short archive already loads quickly, or the browsing experience should work without progressive behavior.
How it works with Faceted Search
Progressive loading and Faceted Search can share the same result area:
- an unfiltered archive can load the next batch as the visitor reaches it;
- when filters, sorting, results-per-page, or faceted pagination become active, Faceted Search controls the updated result set.
Build one clear interaction. Do not place a second unrelated progressive or faceted result area on the same page.
Loading feedback
POM shows a loading indicator while another batch is being requested. Keep enough space around the result area so the indicator is visible and does not look like an empty page.
If a custom loading image is configured for the Faceted Search context, verify its contrast on every background where it can appear.
Images, backgrounds, and layouts
Newly loaded cards initialize their supported images, background effects, video backgrounds, masonry, and other selected feed-template behaviors after insertion.
To keep scrolling stable:
- use consistent image aspect ratios;
- avoid very different card heights when possible;
- provide image dimensions;
- test the first and later batches;
- test taxonomy sections with few and many items.
Category navigation
When a category menu links to sections on a progressively loaded archive, POM keeps the chosen section aligned while earlier content, images, and layouts finish loading.
Test category navigation from:
- the top of the page;
- the middle of a loaded archive;
- a direct URL with a section anchor;
- mobile widths with a sticky header.
Caching
Progressive result requests can be cached by the site or delivery layer. Seeing a result request in browser developer tools does not by itself mean WordPress rebuilt it.
After changing a feed template or archive configuration, clear the relevant page and progressive-result cache through the site's normal cache controls.
Go-live checklist
- [ ] The first result section appears without an excessive delay.
- [ ] The loading indicator is visible and understandable.
- [ ] Later batches use the same card design as the first.
- [ ] Images and interactive card controls work in later batches.
- [ ] Taxonomy sections do not load unrelated content.
- [ ] Facets, sorting, reset, and pagination still work.
- [ ] Category navigation lands below the sticky header.
- [ ] The archive works at mobile width and while signed out.
- [ ] A useful empty state appears when no results exist.