Last I looked at it, Turbolinks parsed the <head> section of the incoming request to see if any assets (which was basically...count the script/link nodes) chang

Last I looked at it, Turbolinks parsed the <head> section of the incoming request to see if any assets (which was basically...count the script/link nodes) changed. If they did, it went ahead and redirected to the requested URL, since it couldn't be sure that assets hadn't changed. This meant that anything page-specific in your <head> caused Turbolinks to double the work your app had do to, and provided no positive benefit at all. I'll check and see how it's behaving now. Edit: Looks like concerned assets are now tagged with a data attribute. Glad that's in there now.