Most WordPress sites are rotting before they launch.
I watch it happen constantly from my desk here in Boise. Someone spins up a new WordPress install, installs fifteen plugins because some listicle told them to, picks a theme that loads 47 JavaScript files, and then wonders why their Core Web Vitals are bleeding red within a month.
TL;DR: I use a specific five-plugin stack on WP Engine with Divi that prioritizes signal density over feature bloat. This post documents exactly what I install, what I refuse to install, and why most “best practices” guides are creating technical debt on day one.
The Cookie-Cutter Launch Problem
The WordPress ecosystem has a bloat addiction.
I’ve audited sites running 23 plugins where six of them did overlapping jobs. I’ve seen starter themes that inject render-blocking CSS for features the site owner never uses. This isn’t optimization. This is structural decay disguised as functionality.
The average WordPress site loads 20+ external requests before the first meaningful paint. That’s not a configuration choice. That’s a liability.
Here’s what happens when you follow generic “best WordPress plugins” guides:
- You install a caching plugin on a host that already handles server-side caching
- You add an SEO plugin, then another plugin for schema, then another for redirects
- You stack image optimization on top of CDN optimization on top of lazy loading scripts that conflict with your theme
The result? A Frankenstein codebase where every new feature introduces a performance tax.
I refuse to build that way.
My Foundation: WP Engine
I host everything on WP Engine. This is not negotiable for client work.
The reason is simple: WP Engine handles server-side caching at the infrastructure level. Their EverCache system eliminates the need for plugin-based page caching entirely. When I see someone running WP Super Cache or W3 Total Cache on a WP Engine install, I know they don’t understand their own stack.
Here’s what WP Engine gives me out of the box:
| Feature | Why It Matters |
|---|---|
| Server-side page caching | No plugin overhead, no configuration conflicts |
| Global CDN | Static assets served from edge locations without additional plugins |
| Automatic daily backups | I don’t need BackupBuddy or UpdraftPlus cluttering my install |
| PHP 8.x support | Faster execution, period |
| Staging environments | I test every plugin change before it touches production |
Golden Fact: WP Engine’s server-side caching eliminates the need for page caching plugins, which are the #1 source of plugin conflicts on WordPress.
This is what I mean by signal density. WP Engine handles the infrastructure layer so I can focus on what actually moves rankings: content architecture, schema implementation, and crawl efficiency.
The Divi Myth
“Divi is bloated.”
I’ve heard this from developers who then recommend themes that load Bootstrap, jQuery UI, and three animation libraries. The hypocrisy is staggering.
Divi is not inherently bloated. Poorly configured Divi installations are bloated. There’s a critical difference.
Here’s how I configure Divi for performance:
- Disable unused modules in Theme Options. If the site doesn’t use the Audio module, it doesn’t load
- Enable Dynamic CSS to generate only the styles each page actually needs
- Enable Dynamic Icons to load icon fonts on-demand rather than globally
- Use the Theme Builder to create lean templates rather than stacking Divi sections with redundant wrappers
The Divi Builder generates clean, semantic HTML when you understand its architecture. The “bloat” reputation comes from users who drag fifty modules onto a page and blame the tool.
I’ve built Divi sites that score 95+ on PageSpeed Insights. The theme isn’t the problem. The strategist is.
The Five-Plugin Stack
Here’s exactly what I install on every new WordPress site I launch. Nothing more.
| Plugin | Primary Function | Why I Use It |
|---|---|---|
| Site Kit by Google | Analytics & Search Console integration | Single source of truth for Google data, no third-party middlemen |
| Yoast SEO | On-page optimization & XML sitemaps | Industry standard, clean sitemap generation, solid redirect manager |
| Imagify | Image compression & WebP conversion | Aggressive compression without visible quality loss |
| Schema & Structured Data for WP & AMP | Advanced schema markup | Granular control over JSON-LD that Yoast’s built-in schema can’t match |
That’s it. Four plugins plus Site Kit for Google integration.
Site Kit by Google
Site Kit connects your WordPress dashboard directly to Google Analytics 4, Google Search Console, PageSpeed Insights, and AdSense if you run it.
Why does this matter? Because I’ve seen sites running three separate plugins to accomplish what Site Kit does natively. One for analytics. One for Search Console verification. One for “speed monitoring.” Each plugin adds database queries and external requests.
Site Kit is a first-party Google product. The data pipeline is direct. There’s no third-party interpretation layer between your site and Google’s systems.
Yoast SEO
I know Rank Math is trendy. I’ve tested it extensively.
I still use Yoast SEO for one reason: stability.
Yoast has been in the WordPress ecosystem since 2010. Their XML sitemap generation is bulletproof. Their redirect manager handles 301s without requiring another plugin. The content analysis features help clients understand on-page optimization without me holding their hand.
Golden Fact: Yoast SEO generates valid XML sitemaps that update automatically when you publish, edit, or delete content: eliminating the need for standalone sitemap plugins.
The free version handles 90% of what most sites need. I upgrade to Premium for clients who need the redirect manager and internal linking suggestions.
Imagify
Images are where most WordPress sites hemorrhage performance.
Imagify compresses images on upload and converts them to WebP format automatically. The aggressive compression setting typically reduces file sizes by 60-80% with no perceptible quality loss.
Here’s what I configure:
- Compression level: Aggressive
- WebP conversion: Enabled
- Resize larger images: Enabled, max width 2560px
- EXIF data: Strip it
Every uncompressed PNG and full-resolution JPEG is a performance tax your visitors pay on every page load. Imagify eliminates that tax at the source.
Schema & Structured Data for WP & AMP
Yoast includes basic schema markup. It’s not enough.
For sites that need LocalBusiness schema, FAQ schema, HowTo schema, or Product schema, I use the Schema & Structured Data for WP & AMP plugin. The granular control is unmatched.
I can define custom schema types per post type. I can inject JSON-LD that targets specific rich result opportunities in Google Search. I can validate schema output directly against Google’s Rich Results Test without leaving WordPress.
This plugin is the reason my clients win FAQ rich snippets and star ratings in search results. Yoast’s built-in schema doesn’t offer this level of precision.
What I Refuse to Install
This matters as much as what I do install.
- Page caching plugins: WP Engine handles this. Installing WP Rocket or LiteSpeed Cache creates conflicts
- Security plugins with firewall features: WP Engine includes a WAF. Wordfence’s firewall is redundant and resource-heavy
- Backup plugins: WP Engine runs automatic daily backups. UpdraftPlus is unnecessary overhead
- “All-in-one” SEO suites that duplicate Yoast functionality: One SEO plugin. Period
- Social sharing button plugins: These load external scripts and tracking pixels. If you need sharing buttons, hardcode them
Every plugin you install is code that executes on every page load. Every plugin is a potential security vulnerability. Every plugin is maintenance overhead.
The signal dense approach means installing only what directly serves your strategic goals: and ruthlessly excluding everything else.
The Forensic Summary
Most WordPress guides optimize for feature count. I optimize for signal density.
My stack: WP Engine, Divi, Site Kit, Yoast SEO, Imagify, and Schema & Structured Data: handles hosting, theme architecture, analytics integration, on-page SEO, image optimization, and advanced structured data. Six components total. No overlap. No redundancy.
If your current WordPress install has more than ten plugins, you’re carrying technical debt. If you’re running a caching plugin on managed WordPress hosting, you’re creating conflicts. If your theme loads resources you never use, you’re paying a performance tax on every visit.
I build WordPress sites that launch clean and stay clean.
Need a forensic audit of your current WordPress stack? I’ll identify the bloat, the conflicts, and the plugins that are bleeding your performance. Reach out here and let’s talk signal over noise.
