As usual xstep provides excellent information
Some things to keep in mind:
1) An export from FCE to quicktime will export it using the sequence settings - which means that if you are using a sequence configured for Apple Intermediate Codec, that's the output you'll get - AIC is an editing codec, not a distribution codec which is why you end up with a 14gig file
(be glad it's not Final Cut Pro, the output file could be significantly larger!
).
2) A "feature length" movie at 733mb is dependent on certain things (basically what X was referring to) like:
a) being heavily compressed using a distribution codec potentially causing severe loss of quality and/or
b) resized to a significantly lower resolution allowing for a lower bitrate which allows for a smaller file yet a crisper image (less resolution can deal with a lower bitrate to maintain image quality).
3) To get the size/resolution/etc. that you want, I'd strongly recommend taking the export from FCE and then using a different program to convert it to an output codec. Although FCE offers export using quicktime conversion, there are tools that make the job more convenient - ie: take a look at something like mpegstreamclip. Even when I used FCE I would never do my recompression thru FCE - I'd export the sequence at its settings and then either use compressor (from final cut studio) or mpegstreamclip to get my final output for distribution.
Aside from the fact that using quicktime conversion thru FCE seemed to guess my framerates wrong often (ie: setting for 30 when it's really 29.97 - causes nice audio drift), it's nice to have a master file that you can run multiple compressions on at different settings without having to have FCE open - especially as you're trying to find settings you like or if you need to do a run later. Programs like mpegstreamclip are up and ready to convert/compress a lot faster then launching FCE just to do another export - especially if it's not a recent project and you have to then load the project after launching FCE (plus dedicated conversion software usually have smaller memory/cpu footprints then a tool like FCE does so more resources can go to your conversion then to keeping the FCE interface up on your screen when you don't need it).