Unless performance is a key component to your service, I would focus on launching and marketing. Being an engineer, I've often fallen into the trap that a product has to be technically perfect before launching. Being a freelancer and indie developer, I've gotten to meet other freelancers and founders, and got to work for agencies and startups.
There's so many products that are technically crap, but they provide value to some people. Thus people are willing to pay for it.
There was one startup guy, who outsourced development to this one guy in Asia. I thought "this product will not last long, if that's the way development is done". He went on to get funding from an investment arm of a big company within the sector. I thought, "ok, this will be as big as it gets". A year later he's got a deal with a major national retailer.
This is one of the reasons I focus on providing value, not a technically perfect product.
I'm not concerned about performance nearly as much as regressions and breakages post-release. Not sure if this is for better or worse, but I'm the only one actively working on this, so I'm trying to streamline the develop-test-publish so I focus more of my time on delivering value when this company properly starts.
It will often be about a balance of speed of development vs stability. And it will be impossible to create something bug free.
I focus more on backups and monitoring. So I might not prevent all bugs from happening, but in case they do - a) I find out very early (error monitoring + uptime monitoring) and/or b) I can roll back very quickly to a very recent version.
I'd rather deliver 6 imperfect features quickly and getting feedback from users early (feedback can mean tracking which features are being used most) and iterating early, than investing a lot of time into 3 technically great features, then finding out 2 of them people aren't really using.
I know it's scary, because it's sort of like going out onto the field without enough training. But focus on the added value you can deliver and listen to your customers, and it will be fine.
There's so many products that are technically crap, but they provide value to some people. Thus people are willing to pay for it.
There was one startup guy, who outsourced development to this one guy in Asia. I thought "this product will not last long, if that's the way development is done". He went on to get funding from an investment arm of a big company within the sector. I thought, "ok, this will be as big as it gets". A year later he's got a deal with a major national retailer.
This is one of the reasons I focus on providing value, not a technically perfect product.