3 ms·
I had the same thoughts. You may be able to reduce bandwidth if you're doing something like responsive images (even then, over a mobile connection, I'd rather l
by WickyNilliams 14y ago
I had the same thoughts. You may be able to reduce bandwidth if you're doing something like responsive images (even then, over a mobile connection, I'd rather low-res images be sent to phone despite the pixel density of my screen), but at the expense of taking longer to start rendering. There's probably a sweet spot between time to render and page weight, but I think this probably makes things worse. I'd rather see things load slowly than double parse the document and see nothing but a blank web page (which i might interpret as the site being completely unresponsive).
Perceived load time is often as important as actual load time. A site that takes 10 seconds to load but spend 80% of that is showing a white screen may feel slower than a website that takes 15 seconds to load but only 10% of the time is white screen.
- shawnjan8 14y agoHundreds of websites use Mobify.js today, and the feedback we get has always been the same - how do you make it so fast?! I completely agree about perceived load time - it is just as important to consider as actual load time, and if Capturing caused a 10 second white screen, then the technology would be not very useful. Luckily, Capturing is very quick, and with the speed of mobile devices greatly outpacing the speed of networks, Capturing becomes even more useful. Plus after the first load, every subsequent page is EXTREMELY fast, due to the library cached and optimized by the JIT. Of course, if you find that the initial white screen is taking longer then you would like, you could easily render out your logo and background color before capturing the document to improve perceived load time :)
- WickyNilliams 14y agoThanks for the response. I will look into this as it's something I am interested in. Can you give me an example of a site using it? So i can get a feel for what's possible