How Jennifer Banz Improved Speed, Security, and WordPress Health After Leaving Cloudways

At a Glance

Key Outcomes

Time to First Byte (TTFB) is critical to overall site health. This single metric impacts every aspect of your website — even a modest improvement ripples downstream through crawling, indexing, ranking, page load, and ultimately user experience.

Testing benchmarks

Every website is benchmarked before and after migration, test yours to compare!

• ttfb.run — Time to First Byte (TTFB)
• securityheaders.ai — Check your security headers

Meet Jennifer Banz

Jennifer Banz runs a high-traffic recipe publishing business built around low-carb, keto, and high-protein recipes for everyday home cooks.

For a publisher like Jennifer, hosting is not just infrastructure. It affects search visibility, reader experience, publishing stability, and the overall speed of the site. Quality hosting is the difference between a site that grows and one that quietly degrades.

The Challenge

JenniferBanz.com did not need a simple lift-and-shift migration. It needed a deliberate cleanup across infrastructure, security, and WordPress health.

The site was running on an outdated stack:

On top of the infrastructure gap, WordPress itself was carrying years of accumulated technical debt:

• WordPress autoload bloated to 801 KB
• Legacy plugin remnants from WooCommerce, Jetpack, Social Warfare, Mediavine, and others
• Incomplete crawl and search indexing configuration
• Orphaned database tables no longer in use
• Security posture that could be significantly improved

The goal was not just to move the site. It was to hand Jennifer back a cleaner, faster, safer platform with a better long-term foundation.

What Crave Hosting Changed

1. Modernized the Entire Infrastructure

JenniferBanz.com moved from a constrained Cloudways environment to a significantly more capable publishing stack. CPU performance increased by 464%, disk I/O improved by over 300%, and the database gained 4x more headroom with 300 max connections and an 8 GB buffer pool.

The difference between profit optimization (Cloudways for Investors) and customer optimization (Crave Hosting for Owners) is clear.

2. Strengthened Security

The site gained Cloudflare Enterprise protection with WAF coverage at the network layer, filtering malicious traffic before it reaches the server. Security headers were improved, and active monitoring was established through WordPress debug logging.

3. Resolved WordPress Technical Debt

Crave identified and removed years of leftover bloat from themes, plugins, and outdated functionality. Autoloaded data — which WordPress loads on every single pageview — was reduced from 801 KB to 509 KB, a 36% reduction.

Removed remnants included data from:

• WooCommerce
• Jetpack
• Social Warfare / Social Pug
• Mediavine
• 1&1 / IONOS Assistant
• Orphaned plugin tables and options

This was a cleanup project, not just a transfer — and part of our zero technical debt promise.

4. Cleaned Up Crawl and Search Configuration

Crave worked through the site's SEO and crawl setup to ensure search engines see what they should:

• Removed Archives pages displaying in Google
• Cleaned up search indexing configuration through Yoast
• Updated robots.txt handling
• Added sitemap link and search filters
• Enabled Author Archives, disabled Date Archives

The Results

TTFB dropped from 507ms to 40ms, a 92% improvement. For a WordPress recipe site, that changes the entire page experience and creates a much stronger base for search and usability.

This also significantly improves:

• Cost of retrieval
• Site crawling
• Content indexing
• Improved ranking

Infrastructure improvements were also substantial:

• CPU benchmark throughput increased by 464%
• Disk write throughput improved by 310%
• Disk read throughput improved by 471%
• WordPress autoload reduced by 36%

Just as importantly, the site is no longer carrying years of accumulated technical debt, incomplete search configuration, or an outdated infrastructure stack.

What Jennifer Now Has Ongoing

Crave's work does not stop at migration.

Industry-First Backups

Crave's backup model follows a 3-2-1 plus cloud approach with 90-day retention:

1. Same server backup on the East Coast for fastest restore
2. Same data center, different server backup for quick restore
3. Alternate data center backup on the West Coast for independent recovery
4. Additional cloud backup for another recovery layer

Most vendors stop at 30-day backups. This approach goes materially further.

WordPress Management

Crave's owner-first WordPress management includes:

• Core, theme, and plugin updates
• Technical debt review
• Full optimization
• Lockdown and hardening

The approach is deliberate, not reckless. Stability, performance, security, and user experience stay tied to the business first.

Business Impact

For Jennifer, this project delivered more than faster hosting. It resolved years of accumulated technical debt, strengthened security posture, cleaned up search configuration, and moved the site onto infrastructure with significantly more headroom.

That means less friction, less hidden risk, and a more dependable platform to keep publishing on — under one accountable provider that takes full responsibility so you can focus entirely on your business and growth.

Final Takeaway

JenniferBanz.com did not just move hosts. It moved to a stronger operating model.

Crave Hosting resolved the technical debt, modernized the infrastructure, strengthened security, improved sitewide TTFB from 507ms to 40ms, and gave Jennifer a faster, safer, cleaner publishing foundation built for long-term stability.