DEV Community

Wangdada Labs
Wangdada Labs

Posted on

WordPress Pre-Launch Checklist: 12 Technical Checks Before You Pay for Production Hosting

The Problem With "Ready to Launch"

Most website crashes and unexpected maintenance tickets happen not because of bad code, but because of omitted operational boundaries during deployment.

Before pointing production DNS to your new WordPress host or upgrading to an expensive managed cloud server, run through this 12-point engineering checklist.

[1. PHP & Environment]   ->  [2. Database & Assets]  ->  [3. Security & Backups]
Memory: 256MB+               Table Prefixes: Custom      Point-in-time Dump
OPcache: Active              Cron: System-level          Automated Restore Test
Execution: 60s+              SSL: Full/Strict            Off-site Cold Storage
Enter fullscreen mode Exit fullscreen mode

Phase 1: Server and Runtime Baseline

  1. PHP Memory Limit and OPcache Verification

    • Ensure memory_limit is at least 256M for standard business sites, or 512M for WooCommerce.
    • Verify that opcache.enable = 1 and opcache.memory_consumption >= 128. Without OPcache, PHP recompiles scripts on every request, creating artificial CPU spikes.

  2. Decouple WordPress Cron (WP-Cron)

    • Disable default request-triggered cron in wp-config.php: 
     define('DISABLE_WP_CRON', true);

  • Set up a real system cron job (crontab) running every 10 to 15 minutes:

     */15 * * * * wget -q -O - https://yourdomain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1
  1. Maximum Execution and Input Vars
    • Bump max_execution_time to 60 or 120 seconds and max_input_vars to 3000 to prevent timeout crashes during bulk plugin updates or menu imports.

Phase 2: Database Hygiene and Asset Optimization

  1. Change Default Table Prefixes

    • Never use wp_ in production. Changing the table prefix to a random 4-6 letter string reduces surface exposure against generic SQL injection attempts.

  2. Image Compression and Off-the-shelf WebP Conversion

    • Raw PNG and JPEG uploads kill Time to First Byte (TTFB) and inflate disk inode usage. Ensure automated conversion to WebP via server module or edge compression.

  3. Object Cache and Transient Cleanup

    • Use Redis or APCu object caching if available on your plan. Check the wp_options table for expired transients and autoloader bloat (keep autoloaded options under 800KB).

Phase 3: Security, Deliverability, and Restorability

  1. Disable File Editing from the Admin Panel

    • Prevent dashboard script injection in wp-config.php: 
     define('DISALLOW_FILE_EDIT', true);

  2. Transactional Email Configuration (SMTP)

    • Never rely on default PHP mail() from shared hosting IPs—your order receipts and password resets will land in spam. Route transactional mail through an API relay (Brevo, Postmark, SendGrid).

  3. The Unnegotiable Restore Test

    • A backup you haven't restored is just a file of hope. Before launching, download a complete backup (files + database) and perform a dry-run restore to a local staging environment.

Operating Budget Rule of Thumb

Responsibility Tier Cash Overhead Time Overhead Recommended Stack
Static / Brochure $12/year (Domain) ~0.5 hrs/month Hugo/Astro on Cloudflare Pages
Low-Traffic WP $40-$90/year ~1-2 hrs/month Standard Shared with daily snapshots
High-Traffic / Store $250-$800/year ~4-6 hrs/month Managed Cloud / Isolated VPS

Interactive Planning & Next Steps

If you are planning an upcoming deployment or auditing your site's ongoing operational costs, explore our independent benchmarks and browser tools at Wangdada Labs:

To simulate your operational hosting costs and test renewal scenarios with custom inputs, check out the client-side, zero-tracking Small Website Hosting Cost Calculator or explore the comprehensive WordPress Pre-Launch Checklist Guide on Wangdada Labs.

Top comments (0)