I’m surprised by how slow the page load speed is, especially for the index page (Leaderboard) and for the Evolution page. I’m using tables in those two pages, whereas I’m using repeating groups in the matches page. Could this be the reason? Are repeating groups better for performance? Or do you see something else which could be slowing things down? I’ve tried removing all players pictures but it didn’t seem to improve performance.
I haven’t worked with tables but also haven’t come across anything on the forum indicating that they’re slower. What jumps out at me when looking at your tables vs RG is that the search constraints in your tables have additional searches
Have you tried returning API calls rather than do a search for? From my experience that’s the fastest way to load bigger data, either that or load it from another API and render that way. My example would be here. This is not a Bubble site, but even if it was, it would load just as fast (the plugins). Reason being, is cause I’m actually pulling ALL my front-end content straight from Notion itself, then rendering it. The actual plugin pages itself are statically rendered (after build) so those will always be fast. The main focus is the load-speed of the data then to DOM.
Another example I can’t really show, but it’s just returning data from a backend workflow and I’m adding that workflow trigger to my API Connector.
Another way to load your data would be in chunks rather than all at once (I go by when the row is visible on the dom, load the NEXT 10 cells, etc).
DOWNFALL: Data is not realtime and needs to be re-rendered/updated. You can rerender data if you put your RG’s in Reusable elements and make a trigger to reload the data (basically a no-code promise).
