No-JavaScript notes

This page attempts to document reasons and demographics for no-JavaScript users.

Unintentional
Users may unintentionally receive the non-JavaScript version, if:
 * 1) They lost connection to the internet midway through the page-load (especially mobile users, and users with unstable wifi connections)
 * 2) Some JavaScript code throws an exception during initialization, preventing further code from loading
 * 3) The user clicks on something on the page that blocks further loading

Intentional
Users may intentionally receive the non-JavaScript version, because:
 * 1) Security
 * 2) For security (JavaScript vulnerabilities in browsers)
 * 3) For privacy (preventing some tracking/advertising systems, usually coupled with disabled cookies)
 * 4) Corporate proxy disabled it (for intranet security)
 * 5) Preference
 * 6) For annoyance prevention (to prevent things like animations, particularly for users who find these overwhelmingly distracting or nauseating)
 * 7) To avoid downloading and executing software that is not freely licensed (since the JavaScript on some sites may be proprietary)
 * 8) Performance
 * 9) For faster site downloading (less to download (bytes))
 * 10) For faster browser rendering (less to calculate (complexity))

Methods for disabling JavaScript

 * 1) NoScript, uMatrix, and similar browser extensions
 * 2) Browser settings (e.g.   option in Firefox)
 * 3) Connection proxy
 * 4) A browser that doesn't support it (lynx, etc.)
 * 5) Developers can use their browser's developer tools to disable JavaScript for specific requests

Tips for developers

 * Use a progressive enhancement approach
 * MediaWiki has  and   classes that CSS can use to target users based on whether JavaScript is run for them. (added in 2011 in T32497)
 * These classes are set on the html-tag, so use selectors and  to remove something from the page.
 * Use your browser's developer tools to test user interfaces without JavaScript enabled

Metrics

 * Global:
 * 2010: 1.6% average (2.06% in U.S., 0.26% in Brazil) (according to developer.yahoo.com)
 * 2013: 1.1% in U.K. (according to gds.blog.gov.uk)
 * 2016: 0.2% average (1.87% in East Asia) (according to blockmetry.com)
 * 2021: NoScript has between 100,000 and 1,000,000 installs on Chrome, and approximately 330,000 installs on Firefox. NoScript is a "recommended extension" by Mozilla, and is one of the very few addons available for Mobile Firefox.
 * (newer stats, and other reliable sources, would be appreciated. Statcounter doesn't yet reveal no-JS usage)
 * Internal
 * 2015: ~3% using browsers that do not support JavaScript per Analytics/Reports/Clients without JavaScript
 * 2016: ~7% of visitors to Wikipedia Portal do not request JavaScript resources per File:Browsers, Geography, and JavaScript Support on Wikipedia Portal.pdf and File:Analysis of Wikipedia Portal Traffic and JavaScript Support.pdf
 * 2020: Per T253033 (methodology in T234865), 13.84% of sub-A tier Desktop, and 36.48% sub-A tier mobile web page views are from browsers without JS support.
 * 2021: Measuring the % of edits coming from users without JS enabled across all Wikimedia wikis: ~6% of logged-in users and ~1% of logged-out users (~5% total). Per T240697.

Sources and further reading

 * On Wikipedia:
 * Unobtrusive JavaScript
 * Progressive enhancement
 * Responsive web design § Mobile first, unobtrusive JavaScript, and progressive enhancement
 * About no JavaScript on Wikipedia:
 * Charlie Owen (2017). "A day without Javascript". "Like a good friend, Wikipedia never disappoints. The site is indistinguishable from the JS version. Keep being beautiful, Wikipedia."
 * On W3C site:
 * W3C Web Standards Curriculum (2011). "Graceful degradation versus progressive enhancement". "It can be said that both progressive enhancement and graceful degradation try to do the same thing: keep our products useful to every user."
 * W3C Web Standards Curriculum (2011). "The principles of unobtrusive JavaScript". "Before we go on to look at practical JavaScript usage in detail, we need to stop and think about how to use JavaScript sensibly so that it doesn’t exclude anyone from your web site. This is the core idea behind unobtrusive JavaScript."
 * Questions on Stack Exchange Network:
 * "Is it worth it to code different functionality for users with javascript disabled?". 2008.
 * "How important is graceful degradation of JavaScript?". 2010.
 * "Should I bother to develop for JavaScript disabled?". 2010.
 * "Should I worry about people disabling Javascript?". 2010.
 * "Why do people disable JavaScript?". 2010.
 * "Difference between obtrusive and unobtrusive javascript". 2011.
 * "Is it ok to require certain users to have JavaScript enabled?". 2011.
 * "Is obtrusive JavaScript ever ok?". 2011.
 * "Browser statistics on JavaScript disabled". 2012.
 * On other sites:
 * WebAIM (2003/2013). "Accessible JavaScript". "It is a common misconception that people with disabilities don't have or 'do' JavaScript, and thus, that it's acceptable to have inaccessible scripted interfaces, so long as it is accessible with JavaScript disabled. A 2012 survey by WebAIM of screen reader users found that 98.6% of respondents had JavaScript enabled. The numbers are even higher for users with low vision or motor disabilities. In short, people with disabilities will experience scripting, so scripted content must be made natively accessible."
 * Web Designer Depot (2010). "How to plan for the absence of JavaScript". "When planning your information architecture and design, you must figure out how to deal with these special groups. I have assembled a few recent real-world scenarios to find clarity on the issue."
 * Emma Patricios (2011). "Why we should support users with no JavaScript". "This post aims to give you some reasons why we should still be supporting users without Javascript."
 * Craig Buckler (2013). "Should users be permitted to disable JavaScript?". "Users will always be able to prevent JavaScript running no matter how vendors show or hide advanced settings – but few will bother. Whether we should cater to those users without JavaScript depends largely on the application you are building. Yet common sense dictates: the more accessible your content, the larger the audience you can attract."
 * Peter Herlihy (2013). "How many people are missing out on JavaScript enhancement?". "This isn't about whether we should offer a good service to non-JavaScript people, progressive enhancement, done well, ensures we always will. But it's interesting to know that 1 in 93 people will experience the design without JavaScript enhancement – especially when it comes to prioritising how much of our time to spend on that design."
 * WebAIM (2014). "Screen reader user survey #5 results". "Prevalence of JavaScript being enabled [97.6%] was down only slightly from May 2012 (98.6%). The vast majority of those with JavaScript disabled were using Firefox (presumably with the NoScript add-on enabled) or were using Lynx on Linux."
 * Ynori Seven (2014). "JavaScript disabled: should I care?". "JavaScript was created as a tool to enhance the browsing experience by adding additional behavioral and interactive features. When did we get to the point where lack of this additional functionality meant the entire process should fail? That's like your car refusing to start because you disabled the radio and the air conditioner."
 * Klint Finley (2015). "I turned off JavaScript for a whole week and it was glorious". "There's another web out there, a better web hiding just below the surface of the one we surf from our phones and tablets and laptops every day. A web with no ads, no endlessly scrolling pages, and no annoying modal windows begging you to share the site on social media or sign up for a newsletter. The best part is that you don't need a special browser extension or an invite-only app to access this alternate reality."
 * Mike Gerwitz (2015). "GitHubbub! GitHub does not value software freedom". "Free software guarantees your freedom to study, modify, and share the software that you use. We value these freedoms on the desktop, so why should we compromise when websites serve proprietary JavaScript just because it creates the illusion of remote execution? When you visit a website that serves JavaScript to the client, your web browser is automatically downloading and executing (often without your permission) ephemeral, unsigned, untrusted software. If that JavaScript is not freely licensed, then the software running in your web browser is proprietary."
 * Andrzej Winnicki (2016). "Just how many web users really disable cookies or JavaScript?". "Our results show UK visitors [to Yell.com] almost always allow JavaScript, with only 0.07% of Yell.com users not allowing JS. This would work out to around 14,000 users out of our twenty million sample, which is a small proportion of traffic and won’t have a big influence on how we design new web applications. Of course, that doesn’t mean we will ignore these users, but we can plan our priorities accordingly."
 * Blockmetry (2017). "What percentage of browsers with javascript disabled?". "From Blockmetry’s direct measurements, 0.2% of pageviews from worldwide traffic across all devices in the fourth quarter 2016 had javascript disabled. Although apparently tiny, the aggregate figure hides a lot of interesting variation and regional patterns, with traffic from some countries having much higher JavaScript disabled rates. Further, cross-tabulating by device type, traffic from desktops, Android phones and Android tablets had the highest rates of disabling JavaScript, while iPhones and iPads generally had lower rates. The next question is: Who disables JavaScript at high rates? The answer is Tor users, east Asian countries, Africa, and Finland. A somewhat unsurprising finding is that 10.5% of pageviews from Tor visitors disable JavaScript. Websites that attract sizeable volumes of Tor traffic need to take note."
 * Vue.js (2017). "Vue.js Server-Side Rendering Guide". "Compared to a traditional SPA (Single-Page Application), the advantage of SSR [Server-Side Rendering] primarily lies in: [1] Better SEO, as the search engine crawlers will directly see the fully rendered page. Note that as of now, Google and Bing can index synchronous JavaScript applications just fine. Synchronous being the key word there. If your app starts with a loading spinner, then fetches content via Ajax, the crawler will not wait for you to finish. This means if you have content fetched asynchronously on pages where SEO is important, SSR might be necessary. [2] Faster time-to-content, especially on slow internet or slow devices."