Improve loading times of demos

[wheresrhys]

It just struck me that the origami registry demos are possibly the slowest loading things I interact with on the internet on a regular basis and does break up the flow (just now I waited so long I forgot what I'd come to the page for).

I don't think the basic architecture of how these are delivered has changed since the very early days of origami - perhaps its something that can be improved upon?

[JakeChampion]

@wheresrhys We recently overhauled how the demos are built and served and they should definitely be faster than previous implementations, but likely could be improved some more.

We are actually replacing the demos on the registry with an Origami StoryBook implementation, I don't think we will work on improving the registry demos anymore and will concentrate efforts on moving to StoryBook

[wheresrhys]

FYI, it was o-message (internal brand) that was particularly slow today - maybe there's some edge case in there which makes it particularly slow.

Looking forward to storybook though

[chee]

it's true, the registry is currently really slow to load demos sometimes.

[notlee]

Definitely worse since the bower to npm migration. @JakeChampion pointed out before that js/css is inlined now which would slow down the initial response and could hurt perceived performance. Not so bad after the first request though thanks to cache. Part of me wonders if it's worth fixing or ploughing ahead with a story book shaped replacement