A little late here, but I just joined. One thing to understand about all of this is that it's probably not due to the adblocker. Developing for anything except Chromium (the browser engine under everything but Firefox and Safari) is seen as difficult and not a first class citizen. Part of this is that on desktop over 70% of users are on Chromium, and on mobile it's 55% (as of October 2024). Given that the rest is divided between Firefox (gecko) and Safari (webkit) that means that those are the first targets for anyone who needs to cut costs.
I would posit that DPReview, having to watch costs, is not running any of their code across either gecko or webkit in any in depth manner. Soon you will have to use Chrome (or Edge, or Brave, or whatever other flavor of chromium you like) or it will just break.
I ran into exactly this yesterday in a video conference with the VA. Their web based conferencing will not work with anything that is not chromium based. I also ran into it with Johns Hopkins (I'm enrolled there).
So anytime you run into these issues, spin up Chrome and see if that fixes it.