4 ms·
Yes, the initial load is heavy. I think lots of it may be device rendering time after the page is loaded- chrome is the only browser that natively renders web c
by caleblloyd 10y ago
Yes, the initial load is heavy. I think lots of it may be device rendering time after the page is loaded- chrome is the only browser that natively renders web components and every other non-blink browser has to wait for polyfills to load. The JS has got to be hard on mobile CPUs especially.
HTTP/2 with server push would help, but I'm hosting on dreamhost shared hosting and they're not HTTP/2 enabled yet. I am using the bundled build option in Polymer which concatenates most of the components, but there's still a lot of assets to serve.
Chrome service worker is working though! Load the site in chrome, then go into airplane mode and hit refresh. (not chrome for iOS though, that's WebKit underneath)
- Mithaldu 10y agoThere's also a simple problem in that you're, on that page, not doing much more than showing simple HTML, however in browsers with JS off, for whatever reason, it shows absolutely nothing. Not even a message that JS is required.