Long place and route after adding logic lock regions

How is a large combinational loop causing long fit times? I'm just curious how the two were correlated, as a long comb loop shouldn't necessarily cause the fit time to go up(yes, the logic of it causes it to go up.) More info on where the compile time is spent is really necessary to make a better guess for solving the problem, since the fitter runs many differnet processes and has different reasons for why compile times could go up. If you want, .zip up your .fit.rpt and attach it, as that provides a lot of information. (I understand you may be sensitive to this and may not be able to...)