Our company website is the same. We just decided it wasn't worth it to cater to EU users, so we geo-blocked the whole continent.
Turning off trackers is harder, you do the same geo IP, but then you have to find all the places you put trackers, and disable them, and test the site without them, and somehow make sure when the next tracker is inserted, it doesn't go to EU. If your code is well managed, it might be easy, but if you're a newspaper, who knows. They may have several different generations of template systems, with older articles staying on what they were published with, or older articles may be static html with embedded trackers.
Supporting the GDPR isn’t free, those technical and legal costs have to be justified by saving an appropriate amount of lost revenues.
All laws are nuanced, just thinking that you are already doing the right thing isn’t enough to avoid legal liability.
Personally I don't have a stake either way in the matter. I can see the argument from both sides. But the entire point of a business is to generate revenue, and we can't do that if we start trying to comply with every local chirp and by-law places decide to pass.