corenominal

Full stack web developer, interested in all the things, but especially the web, code, design, Linux, OS X, PHP, WordPress, JavaScript & robots.

Tagged: performance

Designing for the Appearance of Speed image/svg+xml

The jury has spoken: performance, conversion, and brand engagement are inextricably connected. Amazon has shown that each 100ms of latency costs them 1% in sales. Walmart chalks up an extra 2% conversions with every second of performance improvement. Any online shopper will tell you that faster is better than slower — but is speed as simple as the shortest distance from point A to B?

A look at the importance of perceived speed and how it can help to increase user engagement.

Lighthouse image/svg+xml

Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any page on the web. It has audits for performance, accessibility, progressive web apps, and more.

A nifty tool that provides some helpful hints for improving site performance. I like that it doesn’t just tell you what you’re doing wrong, but shows lots of green ticks for the stuff you’re doing right.

HTTP/2 – A Real-World Performance Test and Analysis image/svg+xml

Our conclusions are therefore:

  1. HTTP/2 is faster in terms of performance and site loading time than HTTP1.x.
  2. Minification and other ways of reducing the size of the web page being served is always going to provide more benefits than the overhead required to perform this “minification”.
  3. Reducing the distance between the server and the client will always provide page loading time performance benefits so using a CDN is still a necessity if you want to push the performance envelope of your site, whether you’ve enabled HTTP/2 or not.

No real surprises, but if you’re interested in implementing HTTP/2, it’s worth a read. Talking of which, I still need to fix this.

Optimising GIFs for the Web image/svg+xml

Interesting that the first tip is to not use gifs at all.

Surprisingly, the lossless compression algorithm used on GIFs is so unoptimised that video formats such as MP4 or WebM will provide a smaller file size than GIF images. Because of this, one solution to the GIF performance problem is to not use GIFs at all, and to replace them with autoplaying, looping, HTML5 Video.