A jQuery-based method for avoiding downloading carousel images until they’re requested:
I’ve implemented something like this before, and would recommend making it fetch the “next” and “previous” images instead of the one actually being requested, to make sure the image is available when it slides onto stage, but an interesting method (using HTML Comments, rather than simply hiding via CSS, which doesn’t work the same everywhere).
The goal was to demonstrate the acceleration benefit (in terms of bytes in, start render time, document complete time, connections, and resources) of each practice for a typical 3G mobile user.
It’s always fun to (quickly) scroll through lists of old, nostalgic JS oddities. But here’s a list of a few current JS oddities; coder beware…
It should never be a question whether ARIA should get added to a site, and yet it still happens. Here’s a simple-to-follow tutorial on helping non-buttons look and act like real-buttons to those that might have trouble realizing it:
Most of this presentation is well beyond me, but the idea of combining these two and getting better performance is all I need to hear…