I haven't tested this as I do not user the who's online module, but I attempted to give a whack at it.

Open mod_comprofileronline.php

and locate:
[code:1]
$query = "SELECT DISTINCT a.username, a.userid, u.name"
."\n FROM #__session AS a, #__users AS u"
."\n WHERE (a.userid = u.id) AND (a.guest = 0) AND "
. ( ( checkJversion() == 1 ) ? "(a.client_id = 0)" : "(NOT ( a.usertype is NULL OR a.usertype = ''))" )
."\n ORDER BY " . ( ( $ueConfig > 2 ) ? "a.username" : "u.name" ) . " ASC";
[/code:1]

Try changing it to:
[code:1]
$query = "SELECT DISTINCT a.username, a.userid, u.name"
."\n FROM #__session AS a, #__users AS u"
."\n WHERE (a.userid = u.id) AND (a.guest = 0) AND "
. ( ( checkJversion() == 1 ) ? "(a.client_id = 0)" : "(NOT ( a.usertype is NULL OR a.usertype = ''))" )
."\n AND (NOT (a.usertype = 'administrator' OR a.usertype = 'super administrator'))"
."\n ORDER BY " . ( ( $ueConfig > 2 ) ? "a.username" : "u.name" ) . " ASC";
[/code:1]

I have not tested this, but it might work. If not it gives you an idea of what you need to do. You can exclude the usertype from the query all together.

Post edited by: krileon, at: 2008/10/05 01:13

NP, you'll always have a delay with any component or module that does a database query. Just typical server behavior.

You might want to consider a more powerful host if you're having "hick ups" on your site, but this all depends on how much traffic you're getting.