When using a database on your site, you can display a large number of items. However, adding too many items to a database can still affect page loading times and overall performance.
How database size affects your site
Super can display database items on your live site without the previous 300-item limitation. However, the more items a database contains, the more content Super needs to load and render on the page.
The number of properties displayed can also affect performance. A database with many items and many visible properties contains more data, which can make the page slower to load.
For this reason, while there is no fixed 300-item limit, we recommend avoiding unnecessarily large databases on a single page.
Multiple views on one page
If you have multiple views of the same database on one page, each view adds content that needs to be loaded.
Using several large views together can increase the total amount of data on the page and may result in slower loading times or rendering issues.
Best practices for large databases
If your database contains a large number of items, consider organizing your content into smaller, more focused pages or views.
For example:
Split your content into category pages
Create filtered views for specific topics or sections
Display only the properties you need
Avoid placing multiple large database views on the same page
These practices can help keep your pages faster, easier to navigate, and more user-friendly.
Keep in mind
There is no longer a fixed 300-item limit for database items in Super. However, the amount of content on a page still matters. Very large databases can require more resources to load, so keeping your databases and pages reasonably sized is recommended for better performance.