Safari vs cross-browser, verified per product. A blocker that works in Safari but not Chrome is a different product from one covering every browser — and vendors describe this differently, so check the exact browsers against your own usage rather than trusting "website blocking" as a phrase. Test before you pay: install, block a test domain, open it in each browser you use.
App plus site together. Blocking instagram.com while the Instagram app sits on the home screen is half a block. Combined blockers close both in one rule; Apple's built-ins require two separate setups. If your habit lives in the app, an app blocker alone may be the whole answer — blocking iPhone apps covers that side.
Granularity. Full-domain blocking ("no youtube.com at all") differs from URL, keyword, or wildcard blocking ("no youtube.com/shorts", "no Wildcard pages"). AppBlock supports URLs and keywords including Safari; Jomo supports wildcards so you can block a page without blocking a whole site; Refocus offers category blocking on Mac. Match the granularity to the habit: feed-specific problems want sub-domain precision, not whole-domain bans you'll delete.
Method tradeoffs, honestly stated. Screen Time and FamilyControls-based blocking use Apple's sanctioned frameworks — no extra configuration, no conflicting with anything, but bounded by what Apple exposes. VPN or profile-based approaches can see traffic across browsers uniformly, but add setup complexity and can conflict with a work VPN or privacy tool you already run. Neither is automatically better; the right one is whichever survives your setup. Fella-relevant specifics: blocking without a VPN and offline blocking.
Strictness, schedules, and temporary access. Same questions as any blocker: does the strict state hold without daily arming, do blocks recur automatically, and does a legitimate five-minute need have a self-closing doorway? See strict blockers and scheduled blocking.