How to fix any SOCIAL COMMENTS added load time

SOCIAL MEDIA COMMENTS are feature-switch options for your WordPress, meant to replace the default WP comment system with an external platform provided comments system. Mostly Facebook or Google Plus as an example; however, it exists a few more dedicated systems, like: IntenseDebate, spot.im, Disqus or Epoch from Postmatic. All these options are packaged in different sizes and various performance dial-downs. Our main issue with these solutions is that they are external solutions - so, there is no room for much WordPress performance optimization. Also, since more basic social media features are already implemented in a typical WP, these always add AGAIN the same server calls to the social media platform. Re-creating the same building blocks for a feature, that was already built by another feature creates extra waiting time for the visitor, adding annoyance. Consider the bellow recommendations when you use these features and enjoy an extra WordPress Speed Up.

How to fix any Social Media Comments added load time?

DO NOT:
1. - Don't duplicate same features added by the implementation provided for Social Media Comments. Check details per example on WHAT TO AVOID AND HOW when dealing with feature-duplication.
2. - Don't use two (or more) comment system in parallel. It is a bad decision, waiting to collide and break both functionalities. Replace native comment system site-wide, if you require social comments.

What Should You Do?
1. - Keep it simple. Use only the most common features with SM Comments.
2. - At every planned maintenance day, after ALL the updates, make sure SM Comments still work.
3. - Put SM Comments on a dedicated page. This will reduce unnecessary load times, when login is not required.
4. - On the SM Comments page don't use any extra features. This will eliminate code collisions and the chance to error out.
5. - Load only when needed. Add a comment button, that redirects to a comment page. Avoid loading time for those, who don't use that feature.

WHAT feature-duplication implementation TO AVOID AND HOW?
1. - Social Login existent already on site combined with Social Media Comments requiring social profile log in. When a visitor is already logged in to your site with FB, then at the comment box it is required again to log in, creates confusion, frustrations, and unnecessary performance issues.
2. - Social Share existent already on site combined with Social Media Comments requiring to share the page you're already on. When a visitor already shared your page, then in the comment box it is required again to share, it creates confusion, frustrations, and unnecessary performance issues.
3. - Social Connection existent already on site combined with Social Media Comments requiring to connect via social media profile on the page you're already on. When a visitor already connected via your page (or it was already connected), then in the comment box it is required again to connect, it creates confusion, frustrations, and unnecessary performance issues.
4. - Social Proof existent already on site combined with Social Media Comments requiring to like the page you're already on. When a visitor already expressed its gratitude (like, +1, tweet, etc) via your page, then when the comment box requires it again, it creates confusion, frustrations, and unnecessary performance issues.