I agree with pretty much what everyone has said before. If you personally dont want to come down on the kid yourself, go to a mentor and ask them to take care of it. However, if you want to do it yourself, dont sugarcoat it. Personally, i'd warn them that i wasnt going to be nice about what i'm going to say, and i have nothing against them personally, but i'm just being blunt to they dont misunderstand me. then i'd blatently tell them it wasnt appropriate as a backup website, explain why, give suggestions on how to fix it (in a question/answer fashion (ex: what are the objectives for the website? do you think this meets the criteria? what do you think should be changed? how could you change this? etc)) and either offer to help them myself, or direct them to another student or mentor that can help them refine what theyre doing. Its all a learning process, and sooner or later, this person is going to have to learn how to deal with harsh critisism. i'm not saying to be harsh, but i'm saying not to completely baby him/her either, because thats not the way the real-world works.
What i do if someone asks me to proofread something they've read (or something to that extent) is i literally tear it apart, explaining what sucks, what needs to be fixed, and praising whats good (if theres any). it seems a bit ruthless, but its highly effective constructive criticism. Once someone knows whats wrong, they're less likely to do it again or forget your point if they dont like you criticizing their work.
just my two cents
