Hey @finedesignz! Since Retool is handling both the backend requesting, response parsing and frontend rendering, it's not uncommon that it can take longer to load, unfortunately. Based on the query you sent, it looks like there's some JS logic also running that might add to the individual query run. If you hover over the time next to your queries, what do the breakdowns look like?\
There are a few general suggestions we recommend that might have an immediate effect on load times and application speed!
1: Caching query results. This would allow you to store your queries for a set amount of time, preventing your application from requesting the data from scratch every single time.
2. Selective query activation. By specifying exactly when you do or do not want a query to run, you can help your application only load and request data when absolutely needed
3. Smaller queries. This one is an obvious one, but it must be listed as a possible option. Loading large amounts of data or having a handful of queries and requests running at the same time could cause some noticeable load issues.
https://docs.retool.com/docs/app-performance-best-practices#debug-query-performance
Update: We also recommend checking out our newer Debug tools in the Debug Console's Performance tab: Debug Tools | Retool Docs . Some other community members talk about how they've used this feature to track down app performance info here too!