Given that we have nothing about your code other than the CGI script names, I can't say for certain if this is a problem. But, in my experience, 90% of the bottlenecks in 90% of all Perl webapps backed by a database is the misuse of the database. If you are backed by a database, a few things to look at:
Are your queries using indices? An index can make the difference between 2 req/s and 200 req/s. (I have personally seen a 99% speed improvement several times.)
Are you using BLOBs to store files? If you are, get them out of the database and onto a NAS. Databases are horrible for storing binary files, such as pictures or audio, and should be used only as a last resort. Better to store the filenames in the database and the files on disk.
Are your tables properly normalized? I don't mean have you followed the rules of normalization to the 5th degree. I meant "Are your tables properly normalized for your needs?" I selectively denormalize for performance on a regular basis, but only after I've properly normalized everything.
Are you executing only those queries that are necessary? This is a Java example, but I once saw a 94% improvement in speed in specific screen in a Struts app by properly configuring Hibernate to not pull the sub-rows for the master query.
My criteria for good software:
Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?