Several jobs back, our development team discovered a little tool that’s become a crucial part of our workflow in optimizing every visual that ends up online for us. The tool is called ImageOptim, and it really does one thing, but it does it so well.
While I’m sure this isn’t a new find for many other fellow front-end developers, we still meet others who don’t know about it, so figured it was worthy of a post this morning.
Read the rest of this entry »
The article linked below goes into some nice detail about improving the speed and perceived speed of a relatively complex WordPress-based web site.
Its biggest point though is in the fact that page speed score shouldn’t overrule actual speed improvements.
Optimizing a Complex Site for Pagespeed
WordPress is great as a content mangement system, but mix in a couple plugins and the like, and some of the optimizations and performance tweaks you’d typically do on a static site go straight out the window.
Taking Control of the CSS/JS that WordPress Plugins Load
I’m a huge proponent of eeking every little bit of speed out of web properties I touch. People’s time is valuable, and their attention spans short. So to me, it’s a win-win to get the best Google Page Speed scores possible. But it’s even better, and even easier to sell to clients when it was first hinted that Google disliked slow web sites, and while a minor factor, still a factor nonetheless in the Google search engine algorithm.
The article below looks at the relation of website speed and search engine optimization value. In short, like everything related to SEO, optimization should focus on customer experience first and foremost. Great results will follow.
The Great Debate: Website Speed and SEO Value
Nice article on getting rid of unused selectors before a site’s CSS goes to the server. I’ve really gotta setup a workflow to do this, most likely via Grunt.
Spring-Cleaning Unused CSS With Grunt, Gulp, Broccoli or Brunch