There are a number of problems with this.
First of all you get 1 MegaBIT per second, whereas this site is 135 kiloBYTES. Put your bandwidth into bytes and you find that you get 125 kiloBYTES per second. Quite a bit different from what you had thought it was.
Secondly you're assuming with your incorrect 600,000 number that traffic comes evenly and uniformly throughout the day, which is incorrect. A number of the websites that I administer recieve over half of their traffic during a daily 6 hour period. I don't know what the spread is at spoofee.com, but I'd imagine that it's somewhat similar.
Then, even assuming that you DO have enough bandwidth on your connection (which you don't) there's the issue of consistency. While it may seem that your service is consistent, unless you do week long bandwidth tests you really can't tell. You also couldn't know whether the service is oversold or not (which is almost certainly is, do you really think that if every single customer started downloading and uploading their limit that you wouldn't experience a slowdown?) unless you're privy to their internal business decisions. Slowdowns that you wouldn't even notice in normal use can be crippling for a web server.
Then of course he has to either buy a webserver or serve from his personal computer. If he's serving from his computer you can expect webservice to gring to a halt anytime he's doing any tasking work or copying files or installing programs. Of course then anytime he has to reboot his computer the server is down for a few minutes. If he buys a server then he has to learn how to administer it, which can be a daunting task itself. Assuming he's not an administrator already and he's setting up his own linux server he can reasonably expect to be rooted within a week, if he's setting up his own windows server it probably won't even take that long.
And what happens when the server goes down? In a datacenter you've got techs monitoring the farm 24/7 who can always be reached to pull the server back online if it goes down for some reason. You also have a server that's shared by lots of other clients, assuring you that as soon as a server goes down, it's almost guaranteed that SOMEBODY will be paying attention to get the techs on the case. If he's out to dinner how does he find out that his server is down to come home and fix it? What about when he's asleep?
But hey, I only do this professionaly, it's not like I'D know anything about it.