#3576 Analyze Allura Tracker front page performance

v1.0.0
closed
Tim Van Steenburgh
sf-2 (994)
General
nobody
2015-08-20
2012-01-12
Mark Ramm
No

Currently from my home network it clocks in at around 4.5 seconds to start serving the page, and 5.5 seconds to all resources loaded.

Figure out what's causing the slow delivery of the initial page. Look at the resource loading and determine if any of the 22 requests can be reasonably eliminated. Look at the "minified"

http://a.fsdn.com/allura/nf/1326133091/ew/_slim/js?href=allura%2Fjs%2Fjquery-base.js%3Ballura%2Fjs%2Fjquery.notify.js%3Ballura%2Fjs%2Fsylvester.js%3Ballura%2Fjs%2Fpb.transformie.min.js%3Ballura%2Fjs%2Fallura-base.js%3Btracker_js%2Fticket-list.js%3Bjs%2Fjquery.lightbox_me.js

Which is just over 344k can be reduced in size. Also look at if it makes more sense to break out a "base" package that will be cached and remain cached rather than downloading such a large file every time new page specific JS is needed.

The objective is to have several performance enhancement tickets ready for the next sprint.

Discussion

  • Tim Van Steenburgh - 2012-01-13
    • status: open --> in-progress
    • assigned_to: Tim Van Steenburgh
     

  • Dave Brondsema

    Dave Brondsema - 2012-01-20
    • size: --> 2
     

  • Tim Van Steenburgh - 2012-02-06
    • status: in-progress --> closed
     

Log in to post a comment.