One of the great things about WordPress is the ability it gives us to extend the capabilities of the core software with plugins. The official WordPress Plugin Directory now has nearly 23,000 plugins. That’s an amazing amount of extra features we can add to our websites.
However the old adage is still true: with great power comes great responsibility. Unfortunately there’s a lot of junk in those 23,000 plugins. You can bog your site down to a crawl, expose your site to hackers or even worse if you aren’t careful.
So here are some things to think about when you are looking for plugins to install. If you pay attention to these things you will be much smarter about the plugins you install. And you will save yourself a ton of grief in the long run.
Before I get down to it, please know this. These are guidelines rather than hard and fast rules.
At the end of the day it is your website and you can do whatever you want. There may be other factors in your case that may cause you to disregard one or more of these considerations.
However, if you at least think through the potential consequences of your choices you will be making much more informed decisions. And it just might help you see some “gotcha’s” before they get’cha, if you know what I mean.
Do You Really Need That Functionality?
So you’ve got your new website. You’ve discovered how easy it is to add plugins from your WordPress dashboard. You went a little wild, didn’t you? You keep seeing cool features on other sites around the web and you want them for your site too.
Now you’ve got a hodgepodge of plugins installed. Dozens of them.
Don’t feel bad. We’ve all been there. The first step in recovery is admitting you have a problem, right?
I once had over 80 plugins installed on one of my sites. Now they weren’t all activated. But that’s still nuts!
My rationale was that I needed to “test” plugins to see what they did so I would know whether to recommend them to my clients. OK. Fair enough. But delete them after you’re done testing them.
That site’s down to 15 active plugins. Much better. Because at the end of the day you really don’t need all that crap (can I say that word here?) on your website.
Before you install a plugin ask yourself what the value of that feature really is. Will it attract more readers to your site? Will it add to the bottom line by helping to increase revenue somehow?
Is it necessary? Or is it just flashy and cool?
If it isn’t contributing to a better user experience, or actively furthering your website objectives delete the plugin. Or better yet, resist installing it in the first place.
Does the Plugin List Compatibility with the Current Version of WordPress?
This one is a biggie. I do a lot of WordPress support and am asked to add and configure specific plugins quite frequently. Assuming we crossed the first hurdle and the functionality is truly necessary, the first thing I look at is what version of WordPress is the plugin listed as being compatible with.
For every plugin in the WordPress Plugin Directory you will see an info box on the top of the right hand column. One of the pieces of info there says:
Compatible up to: 3.5
The number there is the version number of WordPress that the plugin developer says his plugin is compatible with. Ideally that number should be the most recent version of WordPress.
There are a ton of plugins in that 23,000 number that have been effectively abandoned by their developers. Many haven’t been updated in years. WordPress recognizes this as a genuine problem. That is why they started filtering out any plugins that haven’t been updated in the last two years so they don’t show in the search results when you use either the search box on the website or in the “Add New” plugin page of your WordPress dashboard.
Those plugins still show up in Google searches so they added a warning notice to let people know they haven’t been updated in a really long time.
Keep in mind out of date plugins is one of the more common attack vectors that hackers use to gain access to WordPress sites. So having an insecure out of date plugin on your website is a pretty big deal.
Now WordPress just pushed out one of their semiannual (approximately) major updates to the core software and it’s the holiday season. So if a plugin lists the previous version it might not be a show stopper in and of itself. However take that into account when you are evaluating the plugin.
What about paid plugins? Sometimes it’s hard to find any compatibility info listed on plugins available for purchase. If you can’t find the info listed publicly before you purchase the plugin, then reach out to the plugin developer. If they don’t give you a satisfactory answer, move on.
The only thing worse than installing a plugin that breaks your site because it hasn’t been updated in years is paying for a plugin that breaks your site.
Are Support Issues Being Addressed?
Every plugin in the Directory has a support forum where people can reach out for help. Since plugins are offered for free there, the plugin developer has no obligation to support their plugin.
However the best ones always do maintain an active presence and answer questions. That’s one of the things I love about the WordPress community. People are willing to help one another.
However if there are a ton of major issues being raised by users and the plugin developer is no where to be found then maybe that plugin is not the best one for your site.
While you are looking at that, see how many times the plugin has been downloaded. If a plugin has been downloaded hundreds of thousands of times and there are only a handful of people with problems, then it’s likely going to work on your site. But if it has only been downloaded a few hundred times and there are tons of people reporting problems, then steer clear.
Is the Plugin Likely to be Supported Moving Forward?
Now this question is obviously going to be a guess at best. What is the disclaimer that financial advisers use? “Past performance is no guarantee of future results.”
That said going with a particular plugin because it looks good today, only to have it abandoned and have to change to anther solution down the road can be a major pain. This is doubly true if the plugin has a shortcode associated with it that you use. Going through and changing out shortcodes because you need to switch plugins can be pretty tedious, especially if you have a big site with lots of posts using that shortcode.
So what are the indicators that a plugin is likely going to be supported moving forward?
You can look at how long the plugin has been available. If it has a track record of being updated hopefully that means the developer is committed to keeping it going.
How many other plugins does the developer have in the Plugin directory? You can click through the developer’s name on the plugin page and see. If he has several and he seems to be keeping them up to date, then hopefully he’ll keep this one updated too.
That brings us to the last (finally!) big question I look at.
Does the Plugin Developer Have a Profit Base?
To me this question is a big one. A plugin developer that has a reliable income stream that is WordPress related is much more likely in my eyes to keep up with developing a plugin they upload to the Directory than someone who is just playing around.
Sometimes this profit base looks like a premium version of the plugin. Some people get frustrated by paid plugins. But to me that indicates the author is serious about maintaining and improving their plugin. They’ll have to keep it up if they expect new people to pay for it.
Other times the plugin is related to the developer’s main service. For example the NextGen Gallery plugin is now maintained by a company that specializes in developing WordPress websites for photographers. The plugin is free for anyone to use and the developer maintains it because it ties directly in with their own business. It’s in their own best interest to keep up with the plugin.
Or maybe the plugin developer runs a WordPress development/design business. If they’ve been working with WordPress for a few years and it’s now a major income stream for them, then odds are they will likely continue developing the plugin moving forward.
The bottom line is really pretty simple. Taking just a little bit of time to think about your site’s needs and researching the plugin just a little can save you some significant frustration. It can save you from installing a plugin that immediately breaks your site because it hasn’t been updated in years. And it just might keep you from having to go through a painful transition down the road when plugin that is mission critical for your website has been abandoned.