I’ve been doing front-end testing for nearly 8 years now, and if you’re thinking about longer-term JS disabling—maybe across sessions or for specific testing environments—you can go a step further:
Head over to: chrome://settings/content/javascript → Set JavaScript to Blocked by default, then whitelist sites where you want it enabled.
This is ideal when you’re stress-testing a site or simulating environments with JS restrictions—say, you’re checking how a javascript time function-based feature like lazy loading or timeout-triggered UI reacts when JavaScript is unavailable. But yeah, for one-off tests? DevTools is the fastest route.