Journal/Owning your website
Why we don't use plugins
A plugin is a piece of somebody else's code bolted on to your website. Each one is a small risk you did not choose.
12 November 2026·1 min read
Plugins, also called add-ons, are how most template websites get their features. Want a contact form? Add a plugin. A photo gallery? Another plugin. In our own test of twelve WordPress sites, the busiest home page needed 138 files, most of them added by plugins.
The trouble is that every plugin is written by a stranger. They decide when it changes, what else it loads, and whether it carries on existing at all. Each one needs regular updates. Miss an update and you may leave a door open for hackers. Apply an update and two plugins may stop working together, and your site goes blank on a Saturday morning.
Plugins also slow a site down. Each one adds code that every visitor has to download, whether or not that visitor uses the feature.
We write the form, the gallery and the slider ourselves instead. It takes us longer. But the result is a small amount of code that we have read, that does one job, and that will not change unless we change it. Most customers never notice. That is the point.
If your site runs on WordPress today, we have written a fair comparison: a WordPress alternative.

