A new project
As you may or may not know, I am working on something totally different. It's why the Siteimp rewrite is happening in private - the new thing is my main thing right now and I am rewriting Siteimp to solve problems that I am having building it.
The new thing is called Fitness Tracker and I have been using variants of it for seven years. It is more like a mission than a business which could be trouble, but much of my entrepreneurial journey has been defined and enhanced by those sorts of problematic setups.
Siteimp is all over Fitness Tracker, both the website and the application. Siteimp is useful for testing performance in both Tauri and Electron apps though the paradigms are different enough that it has had to evolve to collect different data and prioritize metrics differently in its analysis. As one example, server response time isn't really of much use in a Tauri app (though it can reveal problems in Electron apps). The new Siteimp logger which enables replayability is built into Fitness Tracker and powers customer support.
However, the old version of Siteimp that launched back in 2022 is still heavily involved in my own website development projects. So obviously I use it heavily while I have been building out the Fitness Tracker website. This use of it has shown me that the paradigm Siteimp was built around really doesn't work in the modern web now.
Here is some basic data for you:
- It takes 14.6 seconds for Cloudflare to build and deploy over 1000 files to the Fitness Tracker website.
- It takes 15 minutes to run a full Siteimp report across the entire website.
The second point represents absolutely huge waste - I run Siteimp on my local as a pre commit hook. Since it runs on my local, it isn't subject to any kind of throttling and it will hit the whole site with full force so it's quick and actionable. The full report concept just doesn't work anymore because I already know everything. After projects get pushed into production, Siteimp needs to do a really quick post release verification scan - almost more like an integration test than a classical performance test. We can save the full performance testing for load testing which is where it belongs anyways.