I'm always interested by alternative 'Foxes, but I'm intrigued as to why the installer is about 25MB bigger than Firefox. What's in there that makes it a 50% bigger installer?
ICL creates huge libraries, especially with all the flags I use (-O3 -no-prec-div -Qparallel -arch:SSE3 -QaxCORE-AVX2,CORE-AVX-I,AVX,SSE4.2,SSE4.1,SSSE3). XUL generated like this is about 150MB (and for comparison offical Firefox XUL DLL is about 37MB)!
I'm pretty sure this is because internally, it has multiple copies of the assembly supporting different instruction sets. So it will have a lib with < SSE3, and then another copy of the same code with the SSE4.x optimizations applied. That way you get the speed benefit of SSE4.x on machines that have it, but it can still fallback to SSE3-only if it doesn't have that ISA.
The Microsoft compiler works similarly. This is why "Release mode" builds with optimization on produce bigger binaries than "Debug mode" builds.