When using a database on your site, you may notice that not all items appear on the live page if your database contains a large number of entries. This is usually due to the 300 items per database view limit.
Why is there a 300 item limit?
The 300-item limit exists to help manage page size and server performance. Each database view can display up to 300 items in a single view. If your database contains more than 300 entries, only the first 300 items in that view will be rendered on the live site.
Another important factor is the number of properties displayed in the database view. Each property adds more data to the page. If a view shows many items and many properties, the page size becomes significantly larger. When the page becomes too large, Super may not be able to render it properly.
Multiple views on one page
If you have a database with multiple views, each view can still display up to 300 items. However, placing several large views on the same page can increase the total page size and impact the site's performance. This may lead to slower loading times or rendering issues.
Best practice for large databases
Beyond technical limitations, displaying very large datasets on a single page is not ideal for user experience or SEO. Pages with too much data tend to load slower, are harder to navigate, and may be penalized by search engines.
Instead, we recommend organizing your content into smaller, more structured pages. For example:
Split your database into category pages
Create filtered views for specific topics or sections
Organize entries into multiple smaller views
This approach improves site performance, navigation, and search engine visibility.