Technical Challenges
Creating a website that was bursting with imagery, but keeping the site performant was no mere undertaking. Alongside making an easy-to-use, yet robust CMS dashboard.
The biggest challenge of the Block 16 website of the site was to make the food look good, make Block16 look even better, and ensure the CMS remains usable by two chefs who had never touched a website before. This was accomplished by leveraging WordPress along with Advanced Custom Fields to create a pseudo page builder two years before the Gutenberg block system had been implemented. This system allowed our team to create reusable code blocks which could be added, removed, or rearranged within pages at the whim of the restaurant owners without having to worry about them breaking functionality.
The second biggest hurdle was ensuring that the site was performant for mobile devices. Having a content-rich website full of high-resolution food pictures alongside custom illustrations and video content meant that the site was going to be weighty in terms of page load. This was a problem because, as a restaurant site, a very large portion of visitors are going to be viewing the site from their phones (over 70% according to our metrics at the time), meaning we needed the site to load instantaneously over 3G (or slower) speeds on any device. I ensured that this site had a less than one second load time by leveraging progressive enhancement, image lazy loading, server-side caching, and intelligent font handling so that regardless of visitor device the site would be instantly available so that the restaurant wouldn't lose potential business just because the site was taking too long on their phones.