Why Does Two Cans and String Say It Requires JavaScript?

Updated

Two Cans and String shows the "This site requires JavaScript" message because the page is built to run its content through JavaScript in your browser. Until JavaScript is allowed to run for twocansandstring.com, the site deliberately withholds its content and displays only that notice. The fix is to enable JavaScript in your browser and remove anything that blocks scripts on that domain, then reload the page.

What the message actually means

The notice is not an error from your connection or a sign the site is down. It is a gate: the page checks whether JavaScript is available, and if it is not, it shows the "Whoa, whoa, hold on there. This site requires JavaScript" text instead of the site itself. That is why you see a single line of text rather than a broken layout or a blank white page — the content is never sent to a browser that cannot run scripts.

A practical consequence: there is no non-JavaScript version to fall back on. If scripts stay blocked, the site stays at that message no matter how many times you reload.

How to enable JavaScript and get the site to load

The exact menu names differ between browsers, so treat the steps below as the pattern rather than a fixed path.

  1. Check the browser's JavaScript setting. In Chrome-based browsers, JavaScript is on by default and is controlled under site settings (Privacy and security → Site settings → JavaScript). In Firefox, it lives under Settings → Privacy & Security → Permissions, or per-site via the padlock icon. Confirm JavaScript is allowed, and confirm twocansandstring.com is not in a blocked list.
  2. Allow scripts for this site specifically. Click the padlock or site-info icon next to the address bar and check that JavaScript is permitted for this domain. A site-level block overrides the global setting.
  3. Reload with a hard refresh. After changing the setting, reload the page (a hard reload clears the cached copy). Expected result: the JavaScript notice is replaced by the actual site.
  4. Test in a private/incognito window. If the site loads there but not in your normal window, the cause is almost certainly an extension or a saved site setting rather than the browser itself.

Common reasons JavaScript is blocked

  • Script-blocking extensions. Ad blockers, privacy extensions, and script managers (for example, extensions that block scripts by default) can stop the page's JavaScript. Disable them for this site or pause them and reload.
  • Browser privacy modes or strict tracking protection. Some browsers restrict scripts under stricter privacy settings. Loosening the setting for this site, or testing in a standard window, will show whether this is the cause.
  • Corporate or network policy. On a managed device or network, JavaScript can be disabled by policy. In that case the browser setting may be greyed out, and the fix is with whoever administers the device.
  • A stale cached copy. If the page was first loaded while scripts were blocked, a normal reload may serve the cached notice. A hard refresh or clearing the cache for the site resolves this.

What to expect once JavaScript runs

With scripts enabled, the notice disappears and the site's actual interface loads. If the message persists after you have confirmed JavaScript is on and extensions are paused, the remaining suspects are a per-site block you missed, a cached copy, or a device/network policy — work through those in that order before assuming the site itself is broken.