Gulp And Grunt Tasks For Performance Optimization


Delays in performance have the potential to impact user engagement, experience and revenue. Thankfully, Google’s ‘Make The Web Faster’ team recommend a set of best-practice rules for keeping your pages lean, fast and smooth. These include minifying resources like CSS and JavaScript, optimizing images, inlining and removing unused styles and so on.

If you have complete control over your server, an excellent PageSpeed Module for Apache and Nginx exists with filters for many of these tasks. If not however, or you feel the module isn’t quite for you, a number of build-tasks exist for tools you’re probably already using to fill in the gaps with more granular control.

For a complete list of Gulp and Grunt tasks the Yeoman team recommend for your build process, see my complete write-up on the Yeoman blog.



Deal with something once.

Cross-posted from my article on the Pastry Box

If a task can be done in less than two minutes, do it right now.

I find myself consciously procrastinating more than I would like. I’ll read an email, a GitHub issue or pull request and think “I can come back to this later. I’d rather just code”. Over time the items on my mental to-do list start to build up until I have a decreasing hope of ever getting them complete.

Continue Reading →



The Web’s Declarative, Composable Future.

The way that languages in the web platform evolve are in direct response to the pain caused by complexity. Pain is generally a bad thing and so it’s with better patterns and platform primitives that we can ease some of this complexity in the browser. Complexity on its own can take lots of forms, but when we look at the landscape of how developers have been building for the web over the last few years, common patterns can be one the most obvious things worth considering baking in solutions for. Layering the platform as part of the extensible web manifesto has been hugely helpful in making this possible. Continue Reading →