The speed issues notwithstanding, I don't read anything about your project that would specifically preclude any of the three languages you mention. Large e-commerce sites have been built in all three. I think, in the final analysis, it comes down to personal experience and your own programming "personality." Here's a few thoughts I have:

I have at least a few problems with ASP: 1) it does not meet my requirement of separating executable code from HTML, 2) it is exclusively Microsoft (there are crossover methods like Apache::ASP and Sun's Chilisoft) 3) I'd have to learn VB (too much like the old days).

I have pretty much avoided PHP because: 1) it does not meet my requirement of separating executable code from HTML, 2) lack of 'strickness', 3) too many words--there is a function for *everything*, 4) see the Update from this thread as well as the rest of the discussion.

I like Perl because 1) I know it (fortunately I chose correctly when I decided to learn a server-side language for my web work), 2) it requires me to be a careful programmer (programming has become a hobby for me), 3) and oh...the CPAN modules (I amazed at how a few lines of OO code can eliminate reams of my code and all the headaches), 4) you won't find better support than the Monastery.

The only issue that concerns me about pure Perl/CGI is the overhead, but apparently, though I have never used it and know little about it, mod_perl addresses that.

Whatever you end up using, make sure it is safe, structured, 'strict', uses best practices, and well documented. That will make up a lot of the minuses of any language. Better well-written PHP than poorly written Perl--at least in principle.

PS: Another insightful overview.