I've posted this in the MC forums, but here's a better place: I've been using Loading Profiler to test mods and Doge has some weird results.

Initialization
doge: 3187ms
opencomputers: 1630ms
galacticraftcore: 1179ms
railcraft: 1060ms
buildcraftsilicon: 775ms
forestry: 651ms
pneumaticcraft: 595ms
enderio: 591ms

I'm aware other mods use pre and post as well, but this data is still way over for such a small mod compared to others, and is compared to the total time of the entire Forestry mod.

Yea, i'm not sure why that would be so long. Try running it a few more times, see if it was a fluke. More info on your setup might be helpful to debug.

I've found out that the 1.7.10 version produces similar results right now:

   Initialization
      doge: 3052ms

Which are a non-issue, mostly, so I will close this issue.

I've tried again. and also now without VanillaFix, and the data appears the same.
I am also running FoamFix if it's relevant.

Sorry, but i'm not seeing this either with FoamFix or without.

Mod Loading Profiling Results:
   Constructing
      FML: 158ms
      forge: 80ms
      foamfix: 74ms
      doge: 29ms
      minecraft: 3ms
      loadingprofiler: 1ms
   PreInitialization
      forge: 78ms
      foamfix: 48ms
      doge: 5ms
   Initialization
      doge: 265ms
      foamfix: 14ms
   PostInitialization
      forge: 9ms
   Total Time
      doge: 300ms
      forge: 168ms
      FML: 158ms
      foamfix: 137ms
      minecraft: 3ms
      loadingprofiler: 2ms
      foamfixcore: 0ms
      mcp: 0ms

My only guess is the initialisation stage is where the cape config is loaded. What is your internet connection like?

Australia-like (10 megabit/s). Should be enough for cape textures?

At that stage it only loads a 360 byte json file. I was wondering if it's poor ping which would be plausible if you are in Australia.