It's interesting working for a large employer that relies on ad revenue. Among employees there's understanding that ad blocking bites into our revenue. I'm sure

It's interesting working for a large employer that relies on ad revenue. Among employees there's understanding that ad blocking bites into our revenue. I'm sure some of the employees use ad blockers themselves, though. And when we get customer complaints about the site acting wonky, they're pretty open about using ad blocking. Sometimes it's possible that the ad blocker itself is what causes the issue. There are be a couple of opinions that folks that use ad blockers are on their own and that we won't cater to them, but the more dominant position is that the people complaining are our most active users and help drive engagement, so there's still a strong argument for the site working well in a "degraded" (ad-blocked) mode. There's still a sweet spot to aim for that is ad-compatible. For one thing, limit CLS, because I think content that jumps around due to ads has got to be one of the biggest drivers toward reaching for an ad blocker. Also, some widely-used ad systems are not all that compatible with single-page apps. (Looking at you, gpt.js.) Even if you call their cleanup methods after destroying an ad, you'll have a memory leak on the browser side if you don't completely reload the page/app. So users complain about the SPA "bogging down" as they use it, and they'll often (correctly, even if accidentally) blame the ads. So the ad systems have got to buckle down and fix their own problems if they don't want to drive users toward ad blockers.