You will not always want every item in your query source to load into your Dyggrid at one time. Attempting to built a Dyggrid with thousands of items on a larger WordPress website could result in slow page loading and excessive load on your server.
The number of posts settings allow you to configure the pages size for each load, and optionally limit the total overall items that are returned. Addtional pages can then be loaded based on your Load more settings.
Set this field to the maximum number of posts that should be returned. This is useful if you don’t want your visitors to be able to access more posts using the Load more settings. If for example you had 1000 posts and you set this to 10, only the first 10 posts (based on your Sort order) will be loaded.
Set this to the number of items to be returned on each page. In setting these fields it is good to consider the following:
- How will each page effect your page load time. If for example your Dyggrid loads large images, then you would want to keep this to a smaller number. If it was only building a text based list however, it could potentially be a very large number.
- Larger page sizes are good for cached pages. The first page of each Dyggrid will be cached (if you have a caching capability on your website), so this is likely to load lightning fast. Each additional page however will load via AJAX and in most most cases will not come from the cache. Keep in mind that only the html for the page is cached though not the images for first time visitors.
- What you have below your Dyggrid may never be seen by the visitor. If you configure a grid with Use AJAX load more, and there are a large number of pages in your Dyggrid,, the visitor may never get to the lower content. Your Dyggrid could potentially indefinitely keep adding content that makes the upper section of the page longer.