Of course, faster is always better, couldn't agree more :-)
To be honest with you, when I started working with JUCE, one of the things that impressed me the most (apart from the code itself) is how fast JUCE apps compile compared to apps of similar complexity built with other cross-platform frameworks.
Before I joined the JUCE team here at ROLI, I worked on other frameworks and applications in the music industry, where a real-world app could literally take hours to compile. So companies would buy top-end MacPros and massive build servers for everyone in order for the team to be productive. Using JUCE, I am able to compile a synth on my laptop (!) in a couple of minutes. Personally, I have not seen anything else that performs so well at compile time for this kind of stuff, and it's one of the reasons why I am a JUCE fan :-) Of course, at the end of the day it's up to you to decide what "fast" and "slow" and "normal" means for your use case and what you want to achieve.
Compile time varies depending on what IDE you use. You will probably get better compile times if you upgrade to Visual Studio 2015, and even better compile times if you switch to a Mac and use Xcode.
Also please consider that an app that runs fast is more important for most people than an app that compiles fast. This is the main reason why we use C++ in the first place.