I believe this is due to the manner in which the extension listens for changes to the DOM. It's a bit of heavy code, but generally runs fast. I'll try out a few different approaches and see if I can get away with Firefox not throwing the slow extension warning. Thanks for bringing this to my attention.