The honest answer
A focused MVP can usually ship in a few weeks rather than months — if the scope is narrowed to the single thing that proves the idea is worth pursuing.
The slowest MVPs aren't slow because of code. They're slow because of indecision, scope creep, and premature scaling.
What makes an MVP fast
Pick one job and do it well. An MVP that does one thing convincingly beats one that does five things poorly.
Decide quickly and reversibly. Most early decisions are cheap to change later; treating them as permanent is what creates delay.
Build for today's scale. You can re-architect once you have traction — and you'll do it better with real usage data.