Bookmark URLs take a l-o-n-g time to show bookmark contents in Chrome

Steps to reproduce

In the bookmark pane (in a Chrome tab),

  1. click on a bookmark
  2. copy the url from the address bar (e.g.
  3. open a new chrome tab, paste the url and hit enter

Expected result

Dynalist opens and shows the bookmark content in a fraction of a second (just as if I’d clicked on the bookmark itself)

Actual result

Dynalist opens and takes over 30s to shows the bookmark content (whilst displaying the spinner)


macOS Catalina Version 10.15.7
Chrome Version 87.0.4280.141 (Official Build) (x86_64)
Are you using any third-party scripts for Dynalist, e.g. PowerPack? No

That’s an insanely long time. So, if you just go to and manually click the bookmark, that whole process is way faster? Weird. Try logging into dynalist from incognito mode, loading the document, then pasting the bookmark URL into the same tab. How fast is it then? Then try a different tab. Try different URLs, for nodes, searches etc. Zero in to what exactly triggers the hang.

Thanks for the reply @BigChungus

Incognito tab still takes 30s+
Opening another Incognito to the same url still takes 30s+
A document url is instantaneous in Icognito and otherwise
A global search takes 30s+

A bit baffling

I notice your bookmark has a ?q= in it, meaning you bookmarked a search rather than a node. So, is it fair to say that documents load & refresh within seconds in your browser, but all document searches take 30+ seconds? Wildly guessing as a novice but I wonder if the javascript for search is getting hung on some element in your document…

Is it all documents, or just one of them? Does it happen in Safari too?

Yes the bookmark is the url of a global search.

Yes, it’s all documents and I checked safari, same result.

I think this is due to the issue that when you load the page, it loads the whole workspace before a global search can be performed, coupled with a throttling/rate limiting it’s just getting deferred and waiting until all the documents can be loaded. Totally recommend keeping page loaded and running the query from there for global searches.