If you look at the amount of requests and data that’s being loaded that’s not really a lot in my opinion. According to Opera (gathered at a recent meetup talking to the CEO) the average page size is 2MB so I should be well in the range of file size for a page.
If I look at the network timings in Chrome it is loading quite slow but I don’t know why. I am using Polymer and a lot of webcomponents (although on that particular site not a lot of them are being executed at once). I am not sure how I can figure out what is slowing down the site. Is it something with how resources get loaded or is it how certain stuff is being parsed by the browser?
Thanks, I’ll try to move everything to AWS. Is there another good solution for serving very small static files? I really want to use my free AWS quota as much as possible for the bigger files that get uploaded and downloaded by the site users).
Hmm, serving aws static files didn’t really change anything. The first load is still surprisingly slow. It also can’t be pubs/subs because as of now (fresh deploy) there’s nothing in the database. I’ll be removing web components now to see if it’s polymer slowing things down.
If I were you, I would remove my links to static files to see if this is the cause of the problem. If it is, I would check that AWS is correctly configured for serving static files. If it is not, I would first move my app to a true hosting service (such as DigitalOcean). Given meteor.com erratic performance, I would not trust any measurement on it.
On my fiber connection the site is fast, on mobile the site is slow. There is a 1 mb image that I bet can be compressed. 1 mb images are too much, I skimmed it to 200kb without noticing any change.
If you cant reduce site size (which is not that big actually) consider a premium hosting solution
remember pingdom doesn’t execute JS so you get a wrong picture. Use chrome dev tools for reference.