Plugins that add social sharing buttons should be fairly light and fast — they generally don’t need to fetch much information about a page, like an SEO or SMO / SSO plugin does. Here are some example “execution time” metrics from the P3 (Plugin Performance Profiler) plugin, using WP Test Data, and several popular social sharing plugins (along with the WordPress Core and Twenty Fourteen theme for reference). The plugins were configured to include the Facebook, Google+, Twitter, and Pinterest sharing buttons at the bottom of single posts and pages.
As the name implies, WPSSO SSB works in conjunction with WPSSO, extending WPSSO’s existing settings with additional pages, tabs, and options with social sharing button features. The new settings allow you to include a selection of social sharing buttons in multiple locations:
WPSSO version 2.6 and NGFB version 7.6.1 provide a new ‘Licenses’ settings page to allow for future plugin extensions. Although most of the setting pages and features may not appear to have changed from previous versions, the underlying code – to support future plugin extensions – has undergone important revisions. The ‘Network’ multisite sub-menu has also been renamed ‘Advanced’, and provides a few more cache related options for Network sites / blogs.
NGFB version 7.6.1 fixes a static class reference in ‘NgfbSharing’ for PHP v5.2 and older.
Several websites have reviewed WPSSO in the past few months, and the reviews are all very positive…
“If you want to make every tweet, like, share, pin, and +1 count, then you should definitely start using WPSSO on your WordPress site.” — indexwp.com
The WPSSO and NGFB plugins for WordPress are licensed based on the WordPress Site Address. Typically, a Development, Staging, and Production website – for example – would require 3 licenses. In the spirit of helping our fellow developers, we are offering a free license for every license purchased – on all past and future purchases. So, for example, if you purchased a license for example.com (or www.example.com), you can also register dev.example.com using the same Authentication ID. This allows developers to purchase a license, develop a customer’s website, and then change the Site Address upon delivery, without having to purchase an additional license for the production website.