Share buttons
Share buttons and page speed
Quick answer
Share buttons slow a page when they load third-party scripts, iframes or web fonts from each network, or fetch share counts from the browser. Plain links with inline SVG icons add almost nothing. Measure with a lab test before and after, look at the requests each button adds, and move any count fetching to the server with caching.
On this page
Where the weight comes from
A share link is a few hundred bytes of HTML. What makes some share buttons heavy is everything around the link: official widget scripts from each network, iframes for like buttons, icon fonts, a plugin's own stylesheet and JavaScript on every page, and requests to count APIs made from the reader's browser. The old benchmark post on this domain claimed speed as a selling point, and it was right to: speed is the part of share buttons that affects every visitor, not just those who share.
Measure before you change anything
Pick one post
Use a typical article, logged out, with caching on.
Run a lab test
Record total requests, transferred bytes and the largest contentful paint.
Turn the buttons off
Run the same test again. The difference is the real cost of your share setup.
List the requests
In the browser's network panel, filter by domain to see which calls the buttons make.
Fixes, from biggest to smallest
- Replace official widgets with plain share links. This removes most third-party requests at once.
- Load plugin assets only on templates that show buttons, not on every page.
- Fetch share counts on the server on a schedule and cache them; never from the browser. See share counts not updating for cache settings.
- Use inline SVG icons instead of an icon font.
- Lazy-load anything below the fold that genuinely needs a script.
Profiling in WordPress
Server-side slowness shows up as a slow first byte rather than slow rendering. A query monitoring plugin lists database queries and remote requests per page. If a sharing plugin makes a remote call to a count API while building the page, that call delays every uncached visit. Older profiler plugins were known to misattribute time, so confirm what they report with a before-and-after test.
Questions
Do share buttons slow down WordPress?
Plain share links barely register. Official widgets and browser-side count requests can add many requests and noticeable delay.
How do I find out which share button is slow?
Test a post with and without the buttons and compare the network requests by domain.
Are share counts bad for speed?
Only when they are fetched while the page loads. Fetch them on the server in the background and cache the result.
Hannah Voss, Editor. Checks every guide against a working WordPress install and the networks' current documentation. Last reviewed September 2026.
Related guides
- How to add social share buttons to WordPressAdd social share buttons to WordPress with a plugin, a block, or plain links in your theme. Placement, networks, counts and the checks to run afterwards.4 min read
- Share count not updating or not accurate: a fix listShare counts stuck, stuck at zero or wrong? Work through tokens, caches, cron, URL variants and rate limits in order, and why you should never add fake shares.3 min read
- Share buttons and GDPR: what needs consentWhich share buttons need consent under GDPR and ePrivacy rules, why plain share links usually do not, the two-click pattern, and privacy policy wording.3 min read