# How to fast loading

**URL:** <https://forum.babylonjs.com/t/how-to-fast-loading/25386>\
**Category:** Questions\
**Created:** [November 18, 2021, 8:43am UTC](https://forum.babylonjs.com/t/how-to-fast-loading/25386 "2021-11-18T08:43:15Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![musk](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/musk/32/17156_2.png) [@musk](https://forum.babylonjs.com/u/musk)\
**Post date:** [November 18, 2021, 10:02am UTC](https://forum.babylonjs.com/t/how-to-fast-loading/25386/6 "2021-11-18T10:02:49Z")

</div>

Your model is too large. I don’t know why you need so many vertices. Let me take a wild guess. it don’t use instances. I think the most feasible solution is to optimize your model. Replace meshes with instances whenever possible. Another question is whether you really need to load all assets at once ?  
This topic should be helpful.

> [@Long delay in loading 105 Mb glb file in webpage](https://forum.babylonjs.com/t/long-delay-in-loading-105-mb-glb-file-in-webpage/13911/17):
>
> 1/ The op says they bought the file, so contained the scope of things to do. Even 45 mb seems wildly too much, given the link they provided. 105 mb just for that seems insane. Think the bigger problem is the overkill probably of both # of triangles & texture sizes. But that’s what happens when you get geometry off of others. I got some musical instruments from Blendswap. The keyboard was 2.8 million triangles. Fortunately, a lot of it was due to subsurface modifiers, which divided meshes…

---

_[View the full topic](https://forum.babylonjs.com/t/how-to-fast-loading/25386)._
