CMS Load + Nest causing bandwidth-limit issues from one page

Attributes
, , ,
1

Description

[Attributes V1] This page is transferring far too much data to the viewer, and our Client is hitting their 50gb monthly bandwidth from this page alone. The collections in the 3 tabs on this page are large and have CMS Nesting, but since they are set to CMS Mode: load-under I didn’t think they would be loading more data than is viewable on initial load, unless Load More is clicked, then data would be transferred for the new page of items.

How can I reduce the data transfer to only the elements visible on load, while maintaining search/filter capability of all items at all times?

Alternatively, if I still most load all items in background on load, can I dramatically reduce the amount of data being transferred to the viewer?

Site URL

Required: Please provide a staging/production URL where we can see the issue

Steps to Reproduce

  1. Force-reload page without cache
  2. Check inspector Network tab data transferred

Video/Screenshots

Required: Please provide a short screen recording showing the issue

Additional Context

  • Browser: Chrome
  • Device: Desktop and Mobile
2

Hey @stephen!

The issue most likely stems from CMS Nest performing requests to the template pages to fetch nested items. This happens for every item in the collection list, even those that aren’t rendered.

For large collections with many nested elements, we recommend using CMS Nest Option #2. This setup requires some manual data entry and a slightly modified structure, but it avoids fetching lists from the template page entirely.

Both CMS Load and CMS Nest include a built-in cache optimization (enabled by default). When enabled, these requests only occur on the first page load, improving subsequent load performance.

If you’d like to avoid the double data entry required by CMS Nest Option #2, I highly recommend migrating the entire setup to Attributes v2. It’s significantly more efficient and faster overall.