In reply to Jeff Chandler.

I never had a problem using HTTrack. Using default settings I just took a small snapshot (around 3MB) of wptavern.com without any hiccups. I said small, as I manually cancelled the job as not to abuse the wptavern server. It successfully grabbed the front page and a few of the front page articles (along with their assets) before I stopped it.
It actually has sensible defaults for getting a working local mirror of a website. Most of the options are useful when you realize you don't need everything and you run out of space.

Perhaps you were confused by the fact that httrack creates a single html file as the project's base file, which once you open, provides you with a list of the target URL's you have specified when started the project, and once you follow one of those links, you get your local copy. The actual html files are saved under a subdirectory named after the server's domain name.

Having that said, wget and httrack are two very similar yet totally different tools for me. Both get the job done, however I'd use wget in scripts as it's more generally available, while I'd use httrack for bigger, manually triggered jobs where i'd want to fine tune a lot of options.