Does a LinkedIn widget slow down my website?

What actually loads

With the script snippet, the widget sizes itself to its content, so there are no inner scrollbars or fixed boxes with empty space. The iframe snippet has a fixed height you set yourself.

On your own page, the loader's only jobs are to create the widget's frame and adjust its height; everything else runs inside the frame.

Keep the impact small

• Show what's useful: 3 to 6 posts on a homepage is usually enough. The feed can show up to 30.
• Use shorter post text and hide media in places where a compact list works better.
• Place feeds below the fold when they aren't the main content of the page.
• Prefer the script snippet over the fixed-height iframe where your builder allows it. See script or iframe?
• Several LinkedIn native embeds on one page each load a separate frame from linkedin.com; one widget with several posts is a single frame.
• Paste the loader once per page if you can. If it ends up on a page twice, it doesn't load itself again; it just mounts any new widgets.

How to check on your own site

Run a page speed test such as Lighthouse in Chrome's developer tools or PageSpeed Insights before and after adding the widget, on the same page and device type. Compare the results over a few runs, because scores vary between tests. Focus on what visitors feel: how quickly the main content appears and whether anything jumps around while the page loads. A widget placed below the fold shouldn't change what visitors see first.

If something looks off, check that the snippet was pasted once, not duplicated, and that a caching or optimization plugin isn't rewriting the script. The LinkedIn feed not showing guide covers caching plugins and Content Security Policies.