Here are my takeaways from working the PageSpeed score:
- Render “above the fold” content as soon as possible. No one wants to wait for a page to load while they’re looking for information.
- Keep things fit & lean. A site taking a long time to load is a sign that there’s lots of computing going on (pounding on your mobile phone battery), or there are too many bytes coming over the network (pounding your phone’s data plan), or both. Google isn’t providing all these great developer tools to improve site loading out of altruism – time spent waiting for pages to load is time people aren’t looking at ads!
- Build tools make life a little easier. There are some great open-source tools such Grunt.js that make “trimming the fat” a lot faster by automating many tasks. Thanks & kudos to the Grunt.js dev team. I now see the wisdom in getting a build-tools workflow going sooner in the design
- In the future, I’ll experiment with using a CDN like Cloudflare, Amazon’s Cloudfront to speed-up delivery of parts of the site like images. This might be a good service to offer customers if I get into hosting.
Herding Pixels is a specialty web-design shop that offer mobile-upgrades to small business websites.