Skip to content

Instantly share code, notes, and snippets.

@pavelloz pavelloz/ironadmin.md
Last active Oct 16, 2018

Embed
What would you like to do?
iron admin frontend perf
  • in general you dont want to load too much vendor scripts on pages that dont need it (see webpack code splitting + dynamic imports in webpack docs) and vendors css together (to save http requests) is usually also a good idea (but much easier maintainable when using npm+ (f.e. webpack), especially that css are render blocking
  • you might want to take a look whats inside jquery ui as it is a huge monolith and you probably use like 10% of it, from my experience usually jquery ui is best replaced with something that has been maintained in the last 3 years and is modularized, so you dont have trouble replacing it later on
  • you might want to take a look at slimming down fontawesome you load - by default its very heavy
  • loading only modules you need from bootstrap (both css and js wise) can make it a whole lot lighter
  • light version of normalize.css is included in bootstrap - since you load it in vendors.css, you probably dont need to include it separately
  • your bitmap images could use some compression love, i recommend imageoptim
  • for perf./safety reasons i would move assets from external CDNs (cdnjs) to our cdn
  • <a href="javascript:void(0)"> - this is just wrong ;)
  • if you go to devtools and open command pallette, type "coverage" you can see how much code is used on each particular page - this will give you exact number on why some of the above points are true
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.