Hi,
What are effective items on portal loading speed?

You can use a tool such as Yslow to get a handle on this.

Mainly, though, it's page size, number of items to be downloaded and their size, number of http requests to load the page, etc.

also, some modules developed for DNN 4.x and lower need to have the application pool in iis set to run in 32 bit mode. I had an older version of Dynamic forms on one of our client sites that required this, for example. ^_^

I have also heard that removing unused authentication providers can help, but have not tried this.

In addition, lots of pictures (such as those loaded into a rotating flash module rather than a jquery based one) can slow a page considerably. We try to keep it to 3-4 per module and only one rotator per page if possible!

Thanks a lot! I will check these items.
And if there is a problem, I'll come back!

Certainly you should uninstall modules and other things that you aren't using.  Uninstalling authentication providers not being used is also a good idea.

I don't understand your comment about jQuery rotators, unless you mean that the images are being fetched as needed from the host.

most of the flash and flash modules we have used preload in some form, which seems to slow down alot of the overall page load and functionality - many of the jquery ones load with the page, not before it. Besides which, flash by it's nature is just bigger. I have also had customers uploading unoptimized pics which are HUGE into flash modules that manage the resizing automatically (which, of course,really means it's not resized, just scaled down). This does not mean huge pics or a large number in a jquery based module can't be the culprit - it just seems to have less issues (and usually the images are actual pixel size). ^_^

Hi,
I checked all possible things but it had no result.
My portal has 3 subportals (portal type: child) and all of them have a little contents. Is there any relationship between this and loading speed?

When you refer to loading speed, are you referring to a "first time" page load where the site is starting up for the first time, or after having been inactive?  This is a characteristic of all asp.net websites and is due to the fact that the site needs to be loaded and compiled if it has been inactive for a while.

Mitchel Sellers has a nice series of blog posts on the subject of DotNetNuke performance, and you'll find that here.  He also has written a nice little paper of the subject and it is here.

The website loads slowly in both ways. It has a splash page and we can access to subportals via this page. But both first page and subportals load slowly either I visit them as a guest or editor.
You can visit the portal here: "www.mirdamad-ray.com" .
I'll read those two articles and if the problem doesn't solve, I'll com back again!
Thanks.

Your first page load is slow, so I'm guessing that you will be helped by a keep-alive service or by configuring IIS not to unload the site.  Subsequent loads of the splash page are quick.

I think that once you get past the initial site load and filling the cache with pages, things will be much better.

How can I configure IIS not to unload the site?

I believe that is described in the paper written by Mitchel Sellers.  It is an option for the IIS App_Pool.

Thanks a lot! I found a keep-alive service provider. Also I'm reading Mitchel Sellers's paper.
Which one is more effective, configuring IIS not to unload the site or a keep-alive service?
What if we use both of them?

You only need one.  I've always used the keep-alive service as it's much easier to implement, particularly if you don't have direct access to IIS.

Part of my "standard procedure" is to configure sites per Mitchel's recommendations. 

Now everything is ok!
Thank you!

Great!

There's a good test for site's performance
http://siteloadtest.com

whoops, accidental post - sorry!