# Issue with preloaded data causing x10 slower loading

**URL:** https://meta.discourse.org/t/issue-with-preloaded-data-causing-x10-slower-loading/366612
**Category:** Support
**Created:** [May 18, 2025, 8:09pm UTC](https://meta.discourse.org/t/issue-with-preloaded-data-causing-x10-slower-loading/366612 "2025-05-18T20:09:11Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![pangbo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pangbo/32/538562_2.png) [@pangbo](https://meta.discourse.org/u/pangbo)
#### Post date: [May 19, 2025, 6:21am UTC](https://meta.discourse.org/t/issue-with-preloaded-data-causing-x10-slower-loading/366612/3 "2025-05-19T06:21:01Z")

</div>

![This image displays a performance analysis report detailing the load times for various Ruby on Rails application classes in a Linux command-line interface. (Captioned by AI)](https://global.discourse-cdn.com/meta/original/4X/8/6/4/864cf5d32baef7cca73a4215198a9a12972df5ba.png)

We encountered a similar issue where the query for the topic tracking state consumes approximately 70% of the homepage rendering time. Under high load conditions, this query can even take over 1000 ms to complete.

I think there should be an (optional) approach to make the topic tracking state an asynchronous request, thereby enabling users to view the homepage more swiftly.

---

_[View the full topic](https://meta.discourse.org/t/issue-with-preloaded-data-causing-x10-slower-loading/366612)._