Comments on: LinkedIn CSS Oddities http://rajeev.name/2008/11/19/linkedin-css-oddities/ technologist defying the peter principle Fri, 25 Jun 2010 12:53:52 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Martin Focazio http://rajeev.name/2008/11/19/linkedin-css-oddities/comment-page-1/#comment-22274 Martin Focazio Mon, 30 Nov 2009 13:58:23 +0000 http://rajeev.name/?p=397#comment-22274 This is such a consistent problem that it has rendered LinkedIn as mostly unusable for me. What's most amazing to me is that this is a trivial matter to fix - they need to use a CDN properly - it's not like there aren't a lot of good choices out there for CDN's. It's sloppy, and I'm sure it's part of the reason that LinkedIn is, was, and will be an also-ran in the social networking space. This is such a consistent problem that it has rendered LinkedIn as mostly unusable for me. What’s most amazing to me is that this is a trivial matter to fix – they need to use a CDN properly – it’s not like there aren’t a lot of good choices out there for CDN’s. It’s sloppy, and I’m sure it’s part of the reason that LinkedIn is, was, and will be an also-ran in the social networking space.

]]> By: Alan C http://rajeev.name/2008/11/19/linkedin-css-oddities/comment-page-1/#comment-12434 Alan C Wed, 18 Mar 2009 05:45:24 +0000 http://rajeev.name/?p=397#comment-12434 We were teaching a job search group (Career Connections at Calvary) about using LinkedIn, and ran into problems with this. By opening the Activity window in Safari on a mac, I could see that this static.linkedin.com url was the item that did not load quickly and sometimes completely stalled (well, often). We had to cache the pages and then flip between them later instead of showing live linked in pages in a demo to accompany the slides. Overall network performance speed was 2.5Mbps both ways, which would have been find if the static page were responsive (though I've heard it is very large). Here is a portion (after stripping out the args and %2F, etc) of the url to make it somewhat readable. Effectively, everything after the first token is an arg to that page: static.linkedin.com concat leo yahoo-dom-event yahoo-dom-event datasource datasource-min connection connection-min autocomplete autocomplete-min animation animation-min linkedin-min controls ShowMore MarketingBubble PersonalNav global_navigation container container-min util-min engine-min engine_fix-min ajax ui_settings_service webtracking_service typeahead_service UISettingsService TypeAheadService WebTrackingService I started debugging what was up with the network connection. Now I realize it is not my network connection, but rather these large auxiliary files for the page. Thanks for your post. Let's hope this gets fixed or at least improved. We were teaching a job search group (Career Connections at Calvary) about using LinkedIn, and ran into problems with this. By opening the Activity window in Safari on a mac, I could see that this static.linkedin.com url was the item that did not load quickly and sometimes completely stalled (well, often). We had to cache the pages and then flip between them later instead of showing live linked in pages in a demo to accompany the slides. Overall network performance speed was 2.5Mbps both ways, which would have been find if the static page were responsive (though I’ve heard it is very large).

Here is a portion (after stripping out the args and %2F, etc) of the url to make it somewhat readable. Effectively, everything after the first token is an arg to that page:

static.linkedin.com concat leo yahoo-dom-event yahoo-dom-event datasource datasource-min connection connection-min autocomplete autocomplete-min animation animation-min linkedin-min controls ShowMore MarketingBubble PersonalNav global_navigation container container-min util-min engine-min engine_fix-min ajax ui_settings_service webtracking_service typeahead_service UISettingsService TypeAheadService WebTrackingService

I started debugging what was up with the network connection. Now I realize it is not my network connection, but rather these large auxiliary files for the page.

Thanks for your post. Let’s hope this gets fixed or at least improved.

]]> By: Cooper Marcus http://rajeev.name/2008/11/19/linkedin-css-oddities/comment-page-1/#comment-11974 Cooper Marcus Fri, 13 Feb 2009 19:14:45 +0000 http://rajeev.name/?p=397#comment-11974 Yep, same issue here - was really bad a few weeks ago, seems to have been better recently. Yep, same issue here – was really bad a few weeks ago, seems to have been better recently.

]]> By: Chris http://rajeev.name/2008/11/19/linkedin-css-oddities/comment-page-1/#comment-11265 Chris Fri, 28 Nov 2008 10:14:19 +0000 http://rajeev.name/?p=397#comment-11265 Yes - I've been having the same issue for a while now, seems to be getting worse if anything. I've sent them an email to see if there's a fix coming out. Yes – I’ve been having the same issue for a while now, seems to be getting worse if anything. I’ve sent them an email to see if there’s a fix coming out.

]]>