Tracking Protectection delays requests
When using the private mode on http://www.lensbest.de/ with tracking protection enabled, most requests are delayed by 1-2 seconds. In this time range the loading animation is not present. For example the Links in the menu and in the footer are affected by the problem. If I disable the tracking protection in the address bar, the delay disappears.
I found the Problem in Firefox 42. Reseting Firefox to defaults, and creating a new profile did not help.
Can I do something on the server side to fix this?
When using the private mode on http://www.lensbest.de/ with tracking protection enabled, most requests are delayed by 1-2 seconds. In this time range the loading animation is not present. For example the Links in the menu and in the footer are affected by the problem.
If I disable the tracking protection in the address bar, the delay disappears.
I found the Problem in Firefox 42. Reseting Firefox to defaults, and creating a new profile did not help.
Can I do something on the server side to fix this?
被采纳的解决方案
h.klaus said
When using the private mode on http://www.lensbest.de/ with tracking protection enabled, most requests are delayed by 1-2 seconds. In this time range the loading animation is not present. For example the Links in the menu and in the footer are affected by the problem. If I disable the tracking protection in the address bar, the delay disappears. I found the Problem in Firefox 42. Reseting Firefox to defaults, and creating a new profile did not help. Can I do something on the server side to fix this?
Could be closed. The Problem was caused by a Timeout of Google Tag Manager.
定位到答案原位置 👍 0所有回复 (1)
选择的解决方案
h.klaus said
When using the private mode on http://www.lensbest.de/ with tracking protection enabled, most requests are delayed by 1-2 seconds. In this time range the loading animation is not present. For example the Links in the menu and in the footer are affected by the problem. If I disable the tracking protection in the address bar, the delay disappears. I found the Problem in Firefox 42. Reseting Firefox to defaults, and creating a new profile did not help. Can I do something on the server side to fix this?
Could be closed. The Problem was caused by a Timeout of Google Tag Manager.