I am curious about how DNN and HTTP/2 work together.  It feels like there should be a huge performance boost connecting to outside resources.  I am not sure if current versions of DNN will work the same as .NET Core or if core will provide even more crucial app performance that can use .NET Core.  What in DNN Next utilizing HTTP/2 that will be harnessed to help app loading times that has yet to be put to use and is a big part of the future?

I just feel like every module should be HTTP/2 pushed to the client loading up the theme first then spinners for each module as they load so there is a feeling the page is loading and your ever looking at a blank screen for one second let alone 10 seconds waiting for the site to load you the entire website.  It would give a user a feeling that DNN loaded very quickly and you can look at which module is spinning and maybe even get some reports from it to help develop out faster load times and be able to back it up and brag about it when a vender sells a module.

So an example of performance from an admin perspective is when I go to a site for the first time and it remembers my credentials from being persistent state.  It takes a lot longer than a normal visitor to know you are at the website and loading.  It feels like I should still see the website theme first that then maybe refreshes quickly into what takes a longer time to load with the smallest stuff loaded first to biggest...just so I know I made it to the site right off the bat... creating a sense of performance or speed when you first visit a site.  Maybe this is the login process taking up so much time?  Maybe when logging in the theme gets loaded first then a spinner time killer while it refreshes anything it needs to refresh with any added priviledges.