Ah Ha,
Caveat: I do not use skinny tiddlers, but have a theoretical understanding.
- It would help if you added a splash screen for any Wiki that may load slowly even for people with slow links. see Creating a splash screen
- Second, the advantage of skinny tiddlers is when you only “load on demand”. They would all take time to load. However having skinny tiddlers that always load when you arrive at the site “defeats their purpose”. By definition they should only load after the core and non-skinny tiddlers load.
- Perhaps the common tiddlers and default/at startup tiddlers should not be skinny tiddlers?
On a related note we recently discussed;
- How to reduce the size of your Tiddlywiki
- and here [Discussion] How to reduce the size of your Tiddlywiki
- But it may not be relevant on a node server unless you made core tiddlers skinny.
Others may help more if you detail your host server details.
[edited] Post Script: If the tiddler you display is a compound tiddler drawing on many other tiddlers to generate its content, it may need to load all related skinny tiddlers and again the value of skinny tiddlers is less. Either,
- Don’t use skinny tiddlers, and let the whole wiki load, it will possibly be faster especially if you reassure them with a splash screen.
- And/Or generate a snapshot or static tiddler which is a non interactive copy to deploy at load.
- I went to try and install my tiddler snapshot tool but got an error trying to make the import button visible.