How to improve FCK loading time

The only thing I can think of is that you may be using the original source files for your javascript. An easy way to tell this is to go to your FCK_HOME/fckeditor.js . In there you'll see:

FCKeditor.prototype._GetIFrameHtml = function()
{
        // This should be fckeditor.html for compressed javascript files.
   var sFile = 'fckeditor-original.html' ;

   try
   {
      if ( (/fcksource=true/i).test( window.top.location.search ) )
         sFile = 'fckeditor.original.html' ;
   }
   catch (e) { /* Ignore it. Much probably we are inside a FRAME where the "top" is in another domain (security error). */ }

   var sLink = this.BasePath + 'editor/' + sFile + '?InstanceName=' + encodeURIComponent( this.InstanceName ) ;
   if (this.ToolbarSet) sLink += '&Toolbar=' + this.ToolbarSet ;

   return '<iframe id="' + this.InstanceName + '___Frame" src="' + sLink + '" width="' + this.Width + '" height="' + this.Height + '" frameborder="0" scrolling="no"></iframe>' ;
}

If the sFile variable is set as fckeditor-original.html that means you're downloading all the original source files with your implementation. If you change this to fckeditor.html you will be downloading FCK_HOME/editor/js/*.js instead which is your compressed js file.
The biggest problem with this is if you made any changes to the source files in FCK_HOME/editor/_source/*. If this is the case then you will need to download the FCKeditor.packager.exe which has an easy to follow readme to compress all of your changes into the correct directory.
Hope this helps

http://www.fckeditor.net/demo

http://www.fckeditor.net/demo



http://www.itansvar.se

Before talking with the DotNetNuke developers, someone else should be able to reproduce your problems. It has no sense talk to them:
-"Hey this guy says that he has a problem"
-"Yes, he said it also here"
-"but it works fine for us"
-"also for us"
-"so you don't have a clue?"
-"no"
-"bye"
-"bye"

as a minimum, I would ask you to please set up a demo that can be tested, if this was really a problem in DNN then lots of people would be complaining, not only you.

http://support.microsoft.com/kb/279745