I’m a huge believer in Google Page Speed Insights and getting the numbers as high as possible on every single site I’m involved in. But there’s typically a pair of directives I’ve never been able to affect consistently:
- Prioritize visible content
The article below highlights a possible solution utilizing a Sass @mixin. Though couldn’t the same distinction be made by just having a set of CSS files with one as the priority and the other as below-the-fold, with the additional http request obviously.
jQuery is putting the finishing touches on the final version of its core that will support IE6 and IE7, and another version will drop support for Opera 12.1x and Safari 5.1. At this point, it should disturb and affect very few users, and it makes sense from their stand point. Removing a lot of ancient browser support will clean up and compact the code — both affecting and improving the user experience for the vast majority.
I’ve never had a chance to play around with Node.js, but in some down time did a little quick researching on it and found a lot of easy and different ways to download it and install it locally onto the Mac, but beyond that, I wasn’t sure where to begin, or more importantly — why to begin.
I found the article below that’s a combo introduction / set of examples of where Node.js makes sense, and where it just doesn’t.