Probably because they wait at least one frame before resolving async operations (same behavior with yield return in coroutines). Synchronous operations will almost always be faster than asynchronous, but they also tend to lock the main thread and give a bad user experience. You also can’t synchronously load an asset from a remote location, because that would be locking the application for the duration of the download (browsers don’t even allow it in WebGL).
yes but if I change resources to async too it will bring same result, i think maybe the reason is because resources will be pack inner,but the addressable is a outter packer so should be IO when load by addressable.load