Issue: When testing in a low bandwidth environment the emPath login page can be slow.  Note that this is only an issue when the bandwidth is limited between the webtier and the database tier.  Note that this is not a problem in a production environment.

Resolution: By limiting metatext to one language the login page is much faster.

(1) When testing I often run the webtier my PC and the database on a remote server.   The result is a slow login page.

(2) Through research I found that during the login process emPath reads all of the metatext using by all pages in the application.  More importantly the metatext for all languages is read.   

(3) When possible the login time can be improved by maintaining only one language on the metatext database table.  Realistically this is not always possible.

(4) Note that I don't recommend this workaround for production however it a test environment it is possible to modify the delivered selLocalizationList SQL statement to pull only en_US metatext.  Following is the modified statement:

select  
 US.PAGE_NAME as PAGE_NAME,
 US.ID_NAME as ID_NAME,
 US.ID_TYPE as ID_TYPE,
 US.TEXT_STRING as en_US,
 ' ' as en_CA,
 ' ' as fr_CA,
 ' ' as es_US,
 ' ' as pt_BR,
 ' ' as zh_CN
from
 METATEXT US
where
 US.LOCALE = 'en_US'
order by
 US.PAGE_NAME,
 US.ID_NAME,
 US.ID_TYPE

Note that in production environments in which only US English and/or Canadian English is used then you can improve login response by deleting entries from the metatext table as follows.  (note you should backup the metatext table before running this statement)

delete metatext where locale not in ('en_US', 'en_CA');