When a site breaks, the blocker is not always the cause
The fastest way to find out whether a content blocker caused a problem is to turn it off, and it is also the fastest way to learn the wrong lesson. Half the pages blamed on blockers break identically without one.
Start with a private window
A private window has no extensions and no stored site data, so it separates two very different faults. If the page works there, something in your normal profile is involved. If it fails there too, the site is broken for everyone and no setting on your side will fix it.
Then clear the site's own storage
Stale cookies and cached scripts cause more breakage than filtering does, especially after a site deploys a new version. Clear storage for that one origin, reload, and see whether the fault moves. This step costs ten seconds and rules out the most common cause.
Then disable the blocker for that site only
If the page recovers when filtering is paused for one origin, you have found the cause and you have also found the fix: keep the exception narrow. Whitelisting one site is a decision about one site, not a reason to uninstall anything.
Know which failures look alike
An infinite spinner is usually a script that threw. A layout with missing images is usually a blocked host. A page that loads but will not scroll is usually an overlay, not a filter. Matching the symptom to the layer saves guessing.
Report it rather than living with it
Filter lists are maintained by people who fix reported breakage quickly, and a report with the exact URL and what failed is genuinely useful. Turning the blocker off permanently fixes your afternoon and leaves the list broken for everyone else.
