I have a tiddlywiki that seems to take forever to load. Can someone suggest why and how I can speed things up…
http://cultconv.com/English/Conversations/MacQueen_Mary/TiddlyWiki/indexcopy.html
Bobj
I have a tiddlywiki that seems to take forever to load. Can someone suggest why and how I can speed things up…
http://cultconv.com/English/Conversations/MacQueen_Mary/TiddlyWiki/indexcopy.html
Bobj
You’re right, it does! I nearly gave up while trying to load it to check it out—so my absolute first recommendation would be to use a splash screen, as tiddlywiki.com does, so your viewers know it will load if they’re patient.
Just a few quick impressions! What’s your total file size, out of curiosity?
Edit: Forgot to say—this is obviously a great labor of love, and it’s very impressive!
It took me well over a minute to download your wiki (by right clicking and choosing save as on the link in your post). For a 4MB wiki that is extremely slow.
Once downloaded to my computer, your wiki loads instantly when I click on it. Your hosting service/server is what I recommend looking in to for the slow loading times.
Saqimtiaz, you may be right. Here is another wiki I have been building,. I
Sorry, last reply hit send too early.
I have been playing with another wiki, SES triage — Triaging calls for help. This also loads slow and has only 4 content toddlers and about 5 tags.
The server does host a number of other web pages and they all load ok. So what in Tiddlywiki causes this slow down?
Try h
Etardiff, I have been pondering your point 2. Can you describe how I would use view templates and putting the tags into field(s) to achieve similar behaviour to what is there now.
Bobj
The specifics would depend on your exact needs, but generally speaking:
$:/tags/ViewTemplate
tag will be automatically rendered in each tiddler in the story river. This means that if you still want to have clear access to all the people/places/years/etc. referenced by a page, you could create a few new fields on each Page tiddler–maybe People
Places
Years
, corresponding to tags you’re already using, and populate them appropriately. Then make a new tiddler with the $:/tags/ViewTemplate
tag, perhaps something like this:<$list filter="[<currentTiddler>tag[Pages]]" variable="display">
''People:''
<$list filter="[enlist{!!People}]">
* <$link><$view field="caption">{{!!title}}</$view></$link> <!-- or however you want to render each result -->
</$list>
... etc., for each new field
</$list>
A simple version like this would end up looking a lot like the manually curated lists you have in the body of each Page—and you could, in theory, replace those manual lists, though you’d probably want to merge e.g. Johnson Michael 1938-?
and the currently non-tiddler tag Johnson Michael
.
Or, instead of a link, you could use a button widget (which can look like a link) with a popup that contains a list of other Pages with that field content (<$list filter="[tag[Pages]contains:People<currentTiddler>]"/>
, for instance) and/or other information (a transclusion of that person’s tiddler?)
If you did want something that looked and functioned just like normal tags, but in a different field, you might be interested in the GenTags plugin.
If you do decide you want to do any systematic restructuring (moving tags, adding or removing text to tiddlers in bulk, etc.) I recommend the Commander plugin. I also like SideEditor for working on templates, as it allows you to immediately see the results of your changes in context.
It seems your server has a setting to limit the data-transfer rate for individual files.
TW is an app and not a web page. So it needs to be loaded 100% to be started.
While the text of this page loads reasonably fast. The last element loaded is a PNG image with about 1MByte in size, which needs about 40 seconds on my computer.
So it seems to be a server side setting, that would need to be changed.
This issue with load times, especially with the SESTriage tiddlywiki, begs the question in my mind, how do other tiddlywiki’ers provide acces to their tiddlywiki’s. Are they loaded locally, ie from the device, or are they web mounted?
If web mounted, what have you done to minimise load times, it, as stated above, the whole file needs to be downloaded before rendering can occur?
Bobj
This isn’t a tiddlywiki problem as far as I can tell.
The wiki itself loads basically instantly once all the data is transferred.
There are basically two things you can do:
I’ve have local wiki’s as well as used tiddlyhost, firebase, and pages. All of them worked just fine. I’m not sure why exactly you are having this issue with the server.
Edit: I was curious, so I went to the root site, and basically every page loads at this speed, tiddly wiki is just a bit bigger, and browsers are good at caching images, so you don’t tend to notice on the smaller pages.
Here’s one of my TiddlyWiki instances uploaded to Neocities.
That is over 4MB.
Neocities is a static web server. No backend stuff going on. A link to any file on that web server does nothing more than get that file.
Try opening that TiddlyWiki instance to compare load time with your TiddlyWiki instance.
Charlie,
loading is almost instantaneous. So what did you do?
bobj
I solved a similar problem in the past with a free cloudflare CDN that caches the file on its content delivery network. Some hosts possibly already do this.
Tony,
You still in Sydney? If so, can we get together for a chat? I’d be interested in exploring your knowledge of TW
You can call me on Redacted for safety
bobj
I did nothing at all. That is a stock TiddlyWiki, with the Relink, CodeMirror, and Details plugins.
So the TiddlyWiki HTML file hosted on the Neocities server.
Just to show: your bottleneck is your server. Nothing to do with TiddlyWiki, I strongly believe.
Have been in discussion with my ISP and have also added a loading=lazy attribute to my <img src=… tags.
Can you have a go with
http://cultconv.com/English/Conversations/MacQueen_Mary/TiddlyWiki/index.html
and then try
http://cultconv.com/English/Conversations/MacQueen_Mary/TiddlyWiki/indexcopy.html
and see if there is any difference in loading.
t seems faster to me
bobj
I did not see much difference between the two, but anything over 5 seconds is often thought to be broke, I can’t recommend a splash screen more.
You can even tell them the truth in the splash screen like;
Please wait, loading fast interactive site, in your browser.
After loading once, it is much quicker as long as the wiki file does not change given its locally cached.
Currently, both links are consistently taking about 13 seconds to load each TiddlyWiki instance.
TW_Tones, I have been trying to figure out how to add a splash screen to the wiki or maybe a progress bar. Can not figure it out. Do you have an. Example you could send me.
Bobj