Thing is, I don't see that as confusing at all, as I see what SHOULD be a H1 (the site name/logo), a whole bunch of H2 (all of the golden yellow headings), and H3 under them.... Of course, they don't even come CLOSE to handling it properly as it appears whoever is choosing their tags is doing so presentationally; since all those H3 after the "IMDB Hit List" H2 should also be H2, since they are NOT subsections of 'hit list'.
It's so simple -- "is this the start of a subsection of the heading before it? No, then don't drop to a lower order (higher numbered) heading!"... I don't get why/how people get so confused or find it so difficult. IT'S SO MALFING SIMPLE!!!
But then I say the same thing about "that's not a paragraph", "that doesn't need a div around it" and "that's NOT a definition list" so...
MOST of the problem still remains people thinking what the page looks like when they first build their markup; but again I don't believe in even TRYING to make a layout until AFTER I've semantically coded the content (or at the very least a reasonable facsimile of the content)... because if you don't know what the content is, what business do you have making a layout for it? It's all the "cart before the horse" thinking on web "design" (and if we're talking PSD jockeys, I use the term design in the loosest sense) that results in the needlessly complex, convoluted, and generally not viable for web deployment site concepts that do nothing but flush perfectly good websites down the toilet.
See IMDB -- which was leaner/faster/better a decade ago when it was on HTML 3.2 than the current scripting for nothing, endless code for nothing, two megabytes of being bent over the table by a tranny doctype train wreck.
Which of course means they'll double the code size again when they go to the absolute disaster known as HTML 5.