What does this mean? That you designed it to be inefficient so you can speed it up and gather favor from your users? That you just stopped optimizing halfway through and pegged it 1.0?
Are you a programmer? The idea that there is a finish line for optimizing a program (beyond "This seems fast enough") is weird, and not the sort of thing I'd expect to hear from anyone who's ever done it. You do just have to stop at some point and release. Otherwise you'll keep improving things until the heat death of the universe.
IIRC, the Chrome team has a zero-tolerance policy on performance regressions. Since it auto-updates, it should get faster over time.