Hosting Considerations

3 min read

Your First Technical Decision (Not Your Last)

Let’s flip the typical WordPress development workflow on its head. Instead of picking your plugins and then finding a host that allows them, smart agencies start with hosting requirements. Here’s why: your hosting choice cascades into every other technical decision you’ll make. Government client requiring specific security certifications? That rules out budget hosts. Agency managing 50+ client sites? You’ll want a host with reliable staging environments and painless site transfers (hello, Flywheel). Client already running 15 sites on WP Engine? Congratulations, your tech stack just got simpler because you can leverage their existing security measures, Git deployments, and environment tools.

Think of your host as your foundation, not your afterthought. When you standardize on quality managed WordPress hosts, you get:

  • Pre-optimized server stacks
  • Built-in development workflows
  • Security features you don’t have to cobble together
  • Consistent environments across projects
  • Support teams that actually understand WordPress
  • Clear boundaries on what plugins you can (and shouldn’t) use

The real money-saving move isn’t finding the cheapest host – it’s avoiding the dozens of premium plugin licenses you won’t need because your host already handles that functionality. Your developers will thank you for not making them learn different deployment processes for every client, and your project managers will appreciate having consistent staging environments that actually match production.

Listen to Your Host (They’re Not Just Being Control Freaks)

When WP Engine or other premium hosts say “don’t use this plugin,” they’re not trying to ruin your day. Their banned plugin lists exist because:

  • They’ve already handled that functionality better at the server level
  • Those plugins have repeatedly nuked sites or caused support nightmares
  • They’re redundant with built-in features you’re already paying for

Common Redundant Plugins You Need to Stop Installing

Caching Plugins

  • Your host probably has page caching, object caching, and CDN integration built-in
  • WP Engine’s EverCache > W3 Total Cache
  • Kinsta’s server-level caching > WP Super Cache
  • SiteGround’s SG Optimizer > Yet Another Caching Plugin

Backup Plugins

  • Stop installing BackupBuddy on WP Engine
  • Your host is already doing daily backups
  • They have one-click restore points
  • Their backups actually work when you need them (looking at you, UpdraftPlus on shared hosting)

Security Plugins

  • Many premium & standard hosts already handle:
    • Malware scanning
    • IP blocking
    • Brute force protection
    • WAF (Web Application Firewall)
  • Adding another layer just creates conflicts and false positives

The “But My Client Insisted” Situation

When clients demand specific plugins because they read a blog post from 2015:

  1. Show them the host’s documentation
  2. Explain they’re paying twice for the same thing
  3. Point out that host-level solutions are:
    • Faster (running at server level)
    • More reliable (tested specifically for their infrastructure)
    • Actually supported when things go wrong
    • Included in their hosting cost

Know Your Host’s Stack

Quality hosts often include:

  • Automated SSL handling (goodbye Really Simple SSL)
  • Image optimization services (bye-bye, Smush)
  • Redis object caching (farewell, various Redis plugins)
  • Git deployment tools (see ya, FTP plugins)
  • Development environments (no need for staging plugins)

The Bottom Line

Before installing any performance, security, or infrastructure plugin:

  1. Check your host’s banned plugin list
  2. Review your host’s built-in features
  3. Actually read their documentation (shocking, I know)
  4. Calculate if you’re solving a problem that’s already solved

Remember: The best plugin is the one you don’t need to install. Let your host do what you’re paying them to do.