JavaScript Load Testing

Starting the week of 27 March 2017, Wikia Staff will be testing the loading of JavaScript scripts (JS) here at Admin Tools Wiki (ATW).

Currently, we load scripts here at ATW on a one-by-one basis using importScriptPage. The benefit of this method is that it tends to be most successful in ensuring that all scripts load across all platforms (i.e., desktops, laptops, and tablets (e.g., iPad)). The downside, however, is that it can make page loads noticeably slower on some platforms.

The preferred method to load JS uses importArticles( ), which

can import articles from external communities, bundle several articles into one, minify them and serve them as a single request. This reduces both file size and web traffic, effectively making a community with a large number of additional files load a lot faster.[1]
The downside of this method is that occasionally not all scripts load across all platforms (i.e., desktops, laptops, and tablets (e.g., iPad)).

Nevertheless, ATW and other wikis that load our scripts (e.g., Scratchpad) tend to load a large number of scripts overall. Thus, we would benefit from the importArticles( ) method, if a “fix” could be fashioned so that it would load all scripts across all platforms. It is for this reason that Staff will be performing JavaScript load testing on this site beginning this coming week.

Ambox important Important: Because the process for requesting Testing Administrator privileges here at ATW uses JS, the Requests for rights page will have to be closed until Staff have finished their testing and our JS is back to 100%.

Should you have comments or questions, or should anything need to be reported vis-à-vis the testing, please do so in the comments section below.

Face-smile Thanks!SpikeToronto 09:17, March 24, 2017 (UTC)


  1. From: Help:Including additional CSS and JS/technical.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.