Engadget’s dreadful mobile experience

Most days, I read Engadget waiting for a train, or otherwise in a position where using my phone to read is more ergonomic. I for some bizarre reason still visit Engadget, and again, almost on a daily basis.

Problem is I am forever hounded by this crap.
A massive cookie disclaimer (that is NOT required – when are people going to bother reading up on that law?) and then this content blocking navbar which I really do not need, nobody does, other than when the page loads.

What really pisses me off is that this would have come up before dev even started, every front-ender knows fixed elements are problematic still on mobile browsers, but how could this have made it past the first round of testing let alone to live?

It is such a cheap fix, and so utterly shitty when it comes to the experience of using their site. And don’t get me started on the page jump whilst patiently enduring several MB of ad downloads into incorrectly sized placeholders.