After adding the base recommendation system, I decided to focus on quality. Features are important, but I want Oruwee to provide a better experience than a typical local government website winking Optimization is the first improvement. Oruwee uses a WebAssembly-based framework — it allows a solo developer to build the platform quite fast, but at the cost of website load size and speed. Now this is fixed! The results are pretty good: the first load now transfers 3.5 MB including average content (down from 4.3 MB), and on the slowest devices it takes 47 seconds to load instead of 1.9 minutes. Average load and rendering speed also improved by about 10% across all devices. So Oruwee’s patience test has become a bit more humane smiling_face How was this done? I removed as many external libraries as possible and replaced them with self-made, lightweight solutions. WebAssembly code now also loads in parallel (for geeks: via service workers). It may not sound like much, but building lightweight alternatives turned out to be quite an intensive job.