Thanks to everyone who participated in the challenge! We were quite happy with the quality of the submissions we received, and it honestly wasn’t easy to choose a winner. Keep up the brilliant work!
A few weeks ago, we asked our readers and the community to use everything they could to make their websites and projects perform blazingly fast. Today, we’re thrilled to show off the results of this challenge and announce the winner who will be awarded with some smashing prizes indeed!
What prizes, you ask? The winner wins a roundtrip flight to London, full accommodation in a fancy hotel, a ticket to SmashingConf London 2018, and last but not least, a Smashing workshop of their choice.
Challenge? What Challenge?
Well, the task was not as simple as it sounded. The contestants were asked to improve the performance of a website while keeping the final visual appearance identical before and after. Font loading was allowed to differ, and reflows were acceptable as long as they were kept to a minimum.
While choosing the lucky winner, we looked into the results presented by Lighthouse and WebPageTest, as well as the complexity of the websites our participants had worked on, of course. The first meaningful paint and the time to interactive were the most critical metrics.
But enough hard facts for now. We know you’re curious already, and we don’t want to keep you in suspense any longer. So here it is, the winning project.
And The Winner Is…
The optimization techniques presented in Leonardo’s submission are all DIY, designed and implemented from scratch. He added all the optimizations to PoP, an open-source framework to build websites, and used Agenda Urbana to test the performance improvements on an actual project.
If you’re interested in digging into all the nitty-gritty details of his submission, feel free to do so. We all enjoyed reading the details of Leonardo’s optimizations and felt him a worthy winner due to the sheer amount of work that had gone into this entry.
We were very pleased with the quality of the submissions we received, and it honestly wasn’t easy to choose a winner. Thanks to everyone else who submitted — keep up the brilliant work!
Jorgen Verweij presented an optimized version of his company website Perplex Internetmarketing B.V.. Together with a team made up of a UX’er, a front-end, and a back-end developer, and a system administrator, he set out on the performance endeavor.
The result is an excellent implementation with excellent perf results across the board: SpeedIndex far under their set goal of 1250, a load time of less than 1 second, start render in half a second, a 100⁄100 PageSpeedscore and an almost perfect Lighthouse audit. Compared to the old situation, the load time is almost eight times quicker. Kudos! You can read more details on the process in this comprehensive write-up which Jorgen put together.
Marco Hengstenberg submitted an optimized version of the tourism agency website Land in Sicht. To improve performance, Marco used quite a lot of nifty little tricks and techniques. Preloading the main stylesheet and critical font loading with preload in supporting browsers are only two of them. He also restructured the HTML to make it as flat, semantic and accessible as possible and reduced the amount of data initially transferred on first visit from nearly 3MB to 1.3MB on desktop (and due to the usage of responsive images for the hero image, it is even less than that on narrow screens).
To streamline the site, even more, Marco removed Bootstrap, jQuery, and Modernizr, set up a build process with Grunt, and introduced a ServiceWorker which makes the site available offline, too. The effort was worth it: The result is a dramatic TTL that dropped from 32 seconds to 2 seconds and nearly a 50% decrease in HTTP requests and bytes transferred (also see the Lighthouse report, ZIP 251KB). Preload and quick initial render both help on perceived load time. Great work!
Gabriel also trimmed down the number of fonts being used and set the Google fonts to load in
async so that the critical path CSS will load first. Last but not least, he addressed some other small odds and ends like customizing WordPress plugins, so they rely on ajax instead of PHP. This allowed him to enable page caching and eventually enable a CDN for the site. A switch to HTTP/2 and HTTPS was the final step. See WebPageTest for the full results. Nice!
Alexander Zarges developed Cloud Player, a single page web application based on Angular 4 that lets you search and play YouTube and SoundCloud apps. The upgraded version uses the Angular ahead-of-time compiler to achieve an initializing time of around 2.9 seconds (compared to 5.2 seconds when using the just-in-time compiler). If you want to dive deeper into the code, check out the accompanying GitHub repository.
Bradley Taunt took our challenge as an occasion to experiment with his personal site. As the basis for his optimization undertaking, he used his homepage and an image-heavy article. To slim down loading times to 4.2 seconds for the article, Bradley defaults to the user’s OS System Fonts instead of using web fonts, among other things.
For an extra boost, the optimized version also inlines critical CSS, serves responsive images, and utilizes CDN caching. You can get a more detailed look behind the scenes, in the blog post that Bradley wrote about how he tackled the challenge.
John Beales challenged himself to give 4RoadService.com a performance boost. When he started out there were already some optimizations in place. Static images were run through ImageOptim, for example, CSS and JS were minified, they were running a CDN through CloudFlare, and the site already used a Single-Page-App-style loader so new content is always fetched by XHR and the page is never completely redrawn.
For this challenge, John turned on Image Optimization and WebP compression in Cloudflare. The updated site now uses HTTP/2 Server Push to send out the main CSS and JS files with the initial pageload and relies on Guetzli for JPEG compression. To optimize caching, he updated the URLs of all static assets so that the URL will change whenever the asset changes, then set all static assets to cache for a year. For improved image caching, John also updated the URLs of dynamically-resized images so CloudFlare thinks they’re static image files.
The result: The first meaningful paint dropped from 2,220ms to 1,290ms and the First Interactive from 5,480ms to 3,040ms. You can view the full Lightbox and WebPage Test results here.
Shaun O’Connel’s entry was the work he did on kiwi.ruby.nz. The aim was to turn the conference website into a PWA so conference attendees could look up all information concerning the event offline. Some of the things he did: replacing a typical Google Maps iframe with Google Static Maps, self-hosting subset fonts, moving CSS inline to keep the first request under 14KB, removing dependencies, adding pre-cache Service Workers, and adding Turbolinks for snappy page transitions. By doing so, the initial render time dropped from 3.9 seconds to 0.3 seconds.
For more details check out the WebPageTests.
Ruslan Julbarissow submitted his personal website zerofy.de. Since he finished his optimization work shortly before the contest was published, there are, unfortunately, no detailed before results, but Ruslan made a good write-up of how his tweaks led to a page size of 1.6KB and a TTFB of 197ms. Apart from caching, minifying, GZIP, and jQuery tweaks, he loads fonts afterward to avoid render blocking, and by replacing FontAwesome with a customized IcoMoon set of 10 icons, he managed to save an additional 130KB.
To boost the speed index score and get the fastest experience possible, he also created a separate PHP file which contains all CSS styles affecting the above-the-fold view. A nice detail: The tiny script Barba.js allows him to create page transitions without reloading the whole site.
Thank You To Everyone For Participating
Phew! Now that was quite a challenge indeed! For those of you who enjoy such a good challenge and a brain tickle every now and then, stay tuned for the next challenge. We’ll be coming up with another one in no time — that’s for sure!