Comment 46 for bug 314713

The suggested fiddling with the MTU value hasn't fixed anything here. I discovered that erasing the cookies made it fast until the next cookie was set. You can reproduce it. I haven't had any problems with other sites except linkedin. So I wonder why a network stack should be changed because linkedin is unable to configure their service correctly.

Believe it - it really doesn't work and I'm on Linux since 1996. And believe it, the Web isn't designed in a way to force people to deeply fiddle around in their network settings to make a web site work. I wonder what linkedin feature is causing that harm. Have you spied on xmlhttprequest and javascript to load and transmit things dynamically? Can we isolate the cookie that is causing the issue?