Reduced initial launch time for meteorite applications

Question

I am developing a mobile site where startup time is an important issue. Currently, meteor applications are loading templates for each individual page in the whole application, and it seems that there are no plans to change this to 1.0 , which means an initial hit on launch. In general, the experience has since been really instant, but I'm trying to optimize the first part - esp. on mobile (Asian) 3G networks.

So, what methods are used by people to reduce apparent startup time?

Due to the "full stack" of the nature of the meteor, I am not sure how best to approach this.

For example, having a separate bootstrap / preloader page that loads a meteorite application in the background (iframe?), Then redirects to the meteor’s URL when it’s ready?

Or combining meteors with static pages created by the site and disabling DDP for the first few pages ?

Any accepted methods!

Answer 1

One quick fix you can see for repeat visitors is the Meteor appcache package . With the addition of appcache:

Meteor , - , , .

, . , .

Answer 2

emgee.. fastrender .

Answer 3

This issue was addressed in Meteor 1.5 using dynamic imports. See here .