How are you handling mobile runtime lags caused by resource loading priority?

I’ve been seeing frequent issues where the main thread gets bogged down during the initial asset loading phase when running games on mobile browsers. This often leads to screen freezes or significant rendering delays.

It seems to be a structural bottleneck caused by a lack of asynchronous processing and poor caching policies, especially when calling high-resolution resources all at once without considering the limited memory of mobile devices.

To tackle this, using a lumix solution approach is essential. Practically, we ensure initial entry speed by prioritizing only core data and using lazy loading for the rest, combined with CDNs to reduce physical distance.

However, maintaining consistent performance on low-end devices is always a challenge. How are you specifically managing asset bundling and memory release timing to keep things smooth?

Here is a technical summary of the issue we are addressing:

Mobile Runtime Lag Due to Resource Loading Priority Mismatch

When launching games on mobile browsers, screen freezes or rendering delays are frequently observed during the initial asset loading phase, as the main thread becomes occupied. This is a structural bottleneck stemming from inadequate caching policies and the absence of asynchronous processing that calls high-resolution resources all at once without considering the device's limited memory resources. In practice, initial entry speed is secured by combining lazy loading techniques—which prioritize loading only core data essential for initial startup while calling remaining assets sequentially in the background—with the reduction of physical distance via CDNs. To maintain consistent runtime performance even on low-spec mobile devices, how specifically do you manage asset bundling and memory release timing?

Would love to hear your workflows or any tools you use to automate this!