{"json_modified": "2016-03-28T08:26:23.237871", "uuid": "c81e9dbd-1d7c-428a-8d79-2b731ed7658e", "title": "Optimizing startup performance", "url": "/en-US/docs/Web/Apps/Fundamentals/Performance/Optimizing_startup_performance", "tags": ["Apps", "Games", "Performance"], "translations": [], "modified": "2016-02-29T03:33:10", "label": "Optimizing startup performance", "localization_tags": [], "locale": "en-US", "id": 65843, "last_edit": "2016-02-29T03:32:19", "summary": "Regardless of platform, it's always a good idea to start up as <strong>quickly</strong> as possible. Since that's a universal issue, we won't be focusing on it too much here. Instead, we're going to look at a more important issue when building Web apps: starting up as <strong>asynchronously</strong> as possible. That means not running all your startup code in a single event handler on the app's main thread.", "sections": [{"id": "Starting_up_nicely", "title": "Starting up nicely"}, {"id": "Where_there's_a_will...", "title": "Where there's a will..."}, {"id": "Getting_asynchronous", "title": "Getting asynchronous"}, {"id": "Porting_issues", "title": "Porting issues"}, {"id": "How_asynchronous_should_I_get", "title": "How asynchronous should I get?"}, {"id": "Other_suggestions", "title": "Other suggestions"}, {"id": "See_also", "title": "See also"}, {"id": "Original_Document_Information", "title": "Original Document Information"}], "slug": "Web/Apps/Fundamentals/Performance/Optimizing_startup_performance", "review_tags": []}