There are several factors that can impact the form/portal performance and cause it to slow down.

When a form loads multiple linked record fields (with child records), a noticeable slowdown is expected. This happens because the data is being retrieved from other tables, which can add a few extra seconds to the load time for each table.

Linked record fields are related to child forms, which exist as distinct entities. They fetch data from another table, thereby contributing to an extended loading time for the form or portal. You can draw a parallel by comparing a form featuring multiple linked record fields with one encompassing just a single linked record field, and the difference in loading time becomes apparent.

The grid/gallery supports pagination by default to speed up loading times. It limits the number of shown records to 100 and allows users to click "more" to load the next page. But if you have a lot of records and/or a lot of images, the performance may become slow. We recommend reducing the number of records by using filters to control the view. For example, you could create different views for different groups of records, instead of just having one large view with everything.

You can hide some fields so that only the most important fields are shown by default. Users would need to click to expand the record and see the rest of the fields. This will greatly speed up the portal loading time, since far less data needs to be fetched and displayed at the same time.

This is a possible reason for slow performance in a gallery view, especially. If you have very high-resolution images, we recommend resizing these images for them to load faster. You can use one of our automatons to do that.

The Airtable API normally allows a standard request rate of 5 requests per second. However, if you reach your monthly limit in Airtable, the rate is reduced to 2 requests per second, impacting the speed of extensions.