People love wordpress.
I get it: I love WordPress, too. It is reliable, generally secure, and allows your customers to easily edit, add, and update their content.
WordPress is a wonderful tool that can be used to build some impressive website, integrate storefronts, and do all sorts of nifty things.
And there’s so much more to love about it: The community is active and engaging; the plugin market is massive; their hooks and loops systems are easy to understand and use; their templating system makes sense; their support is incredible; and on and on….
But is it right for your project?
All of the things we know and love about WordPress don’t come for free, though.
While you may not pay any money for WP, there is a hidden cost you probably aren’t considering.
Namely: WordPress is fucking huge.
I’m building a new WordPress skin for an old client of mine, Andy Ziker, and in the process of doing so decided to update my home rig.
I have been using WAMP as my home server software for years, and it’s served me well, but lately it hasn’t been a good fit.
I needed to update, so I removed WAMP and switched to XAMPP, which overs me more control and is kept more up-to-date.
Because of this change, I had to reinstall a local copy of WordPress - software I haven’t personally downloaded and run in years.
In the process of installing WordPress I had to copy all of the core files into my htdocs directory, which lead me to a realization: WordPress is seriously the biggest damn piece of web software I’ve ever seen.
It took me like 10 minutes to unzip everything to the htdocs folder.
It was some 1,200 or more files - not including theme files and plugins.
Just think: Every time you build a client site on WordPress, their visitors have to load all of that shit.
And most “web designers” these days don’t actually know how to code
php or build anything in WordPress, so instead of starting with something like _s, and stripping away the bloat to keep only the necessities, they just load up genesis or the Divi theme and fuddle around with the options.
Both of those things - and the other things people use like Visual Baker and Beaver Builder - are all just huge and bloated.
And this lack of knowledge when it comes to even basic coding means you rely on plugins to achieve the most basic effects - because you don’t know how to utilize WordPress’s hooks and run a
Now you’ve got 38 plugins running on client’s site - 12 of which do things WordPress already does natively.
All of this, and your client’s website has a grand total of 3 pages: Home, About, Contact.
Why not just build a static site? It will load faster, be more secure, and its doubtful that your client will ever need to really update anything.
If your project doesn’t involve heavy blogging, has less than 10 pages, and doesn’t require ecommerce, there is really no reason to build anything other than a static site.