See Title for overview. Additional background:

• The problem in more detail: on the computer I'm using it normally browses & researches the web just fine however {on these URLs: https://wiki.js.org/modules +https://wiki.js.org/feedback +https://wiki.js.org/about } that header {decorative animation: displays as moving background star/bead streams} causes the computer to slow down just enough that typing & navigation slows to where it's notably unpleasant to type while any of these pages is displayed in a tab... even to just take notes on these very pages! -so a notable downer for me to 1st learn of this otherwise impressive-sounding wiki software!

•• So I check Chrome Task Manager and indeed it reports this page is using highest CPU of any tab, notably causing wiki.js.org at CPU~65 +GPU Process at CPU ~80.

•• FYI I'm using a https://www.newegg.com/gateway-sx-series-sx2800-07-student-home-office/p/N82E16883113125 (yeah old BUT) 8GB RAM running Windows latest (v10) & Chrome latest which again browses & researches the web just fine except also great for detecting CPU wasting & hording software including web pages with needless animations as these.

• And I find no good fixes:

•• first no way to turn off decorative animation -PLEASE ADD and keep OFF by default if non-trivial CPU,

•• also hacking the page HTML/JS with F12 to fix is looking pretty hard,

•• also chrome://settings/content/javascript?search=javascript adding ‘[*.]wiki.js.org’ kills all JS so then the pages display nothing,

•• also creating {archives of latest pages: https://web.archive.org/web/20200227083602/https://wiki.js.org/about +https://web.archive.org/web/20200227083357/https://wiki.js.org/feedback +https://web.archive.org/web/20200227083129/https://wiki.js.org/module} fails to readably archive as presumably the JS not fully running prevents content display

••• another good thing to fix is to enable these readably archive by leader Archive.Org -including that also allows public universal historical archive even if the domain name goes away or changes.

• But fortunately the fixes I suggest, at least to disable this JS, should be easy to do o by the web pages authors.

• So please fix esp so these key +introductory pages are readable by most anyone w/o system-slowing pain; and kindly in general naturally never risk placing aesthetics over good-function.