I don't want to learn some toy language.My advice is to learn a toy language.
This is where your analysis paralysis is coming from. You need to come to grips with the terrible realization that nobody cares whether your web app is built out of a "serious" language or a "toy" language. People care what the app does. The ratio of the number of visitors to the number of people who will ever see your code is going to be a thousand to one, and that's if your app is a failure.
Web publishing is about the content. Deliver the goods. Use whatever is handy. There are about a thousand ways to build a web app, and most of them work. As a rule of thumb, the stupidest thing that could possibly work is the best approach to a new problem. If static HTML works, use static HTML.
The other thing to realize is that you need to learn many approaches. You will attack problems of many different complexities. You will solve problems that will take you years, and you will solve problems that should take you minutes. You will be programming for years and years, so you have plenty of time to learn some "toy" languages and some "serious" languages and everything in between.
Here are some exercises. Do them in any order. Do them fast. These are toys, so don't forget to smile while you're playing with them.
Build the best web page you can using nothing but HTML, CSS, and static assets. Practice thinking and working like a designer.
Build the best web page you can using only Javascript, HTML, and CSS. Client-side Javascript for starters. Then look into server-side Javascript.
Build a website the old-school way. Use PHP and MySQL. Bonus points for skipping the PHP and working directly in C. No frameworks, no Django or Rails, no OOP.
Write a web server in C. You say you can handle C? Now's your chance! It doesn't have to be a fancy web server: Write the dumbest web server you can, serving up HTTP GETs. Once it works, aim some tool like Siege at it and make it cry bitter tears. Compare its performance to, say, nginx. See if you can figure out why your web server sucks compared to nginx. See if you can at least double the throughput of your web server.
Build a site in Drupal. (Shameless plug: www.drupalgardens.com. But don't forget to export your code, put it on your own server, and install a module or two just to prove you know how. You're a CS student, after all.)
Build a web app using Rails. Google Michael Hartl Rails for help. Tell him he owes me a dollar for the plug. ;)
Build a web app using one of the many Lisps. Arc, Racket, Clojure, Common Lisp, take your pick.
Build a web app in Erlang, Haskell, or Factor.
Meanwhile, and now I'm being totally serious: Learn Emacs, VI, or Textmate. Learn Git, Bazaar, or Mercurial. Learn to install Linux on a VPN. Learn regular expressions. These things are not toys; these are going to be your bread and butter.