A host can meet WordPress minimum compatibility requirements and still be a poor home for a business website. Evaluate the current software environment, resource limits, backups, support and exit options together.
Current software recommendations
At the date checked, the official WordPress download page recommended PHP 8.3 or greater, MySQL 8.0 or MariaDB 10.11 or greater, and HTTPS support. WordPress may continue to run on some older environments for compatibility, but an end-of-life runtime is not a sensible target for a new business site.
| Area | Minimum question | Better business standard |
|---|---|---|
| PHP | Does the host support the WordPress version and all required extensions? | A currently supported PHP release with a safe test-and-rollback path for upgrades |
| Database | Is a compatible MySQL or MariaDB version available? | A supported database version with backups and monitoring |
| HTTPS | Can a valid certificate be installed? | Automatic renewal, forced HTTPS and no mixed-content issues |
| Web server | Can WordPress permalinks and required rules operate? | Documented configuration and competent support |
| Resources | What memory, CPU, process and storage limits apply? | Limits suitable for traffic, backups, imports and scheduled tasks |
| Can the site send reliable transactional messages? | Authenticated delivery through a suitable mail service with monitoring |
Backups and restoration
Ask for the backup frequency, retention period, storage location, exclusions and restore process. A backup controlled only inside the same hosting account is weaker than a separate copy. The decisive test is whether a representative restore can be completed, not whether the control panel displays a backup icon.
Staging and change control
A staging environment is useful for plugin, theme, PHP and major content changes. Confirm whether the host copies the database safely, prevents search indexing, protects customer data and supports selective deployment rather than blindly overwriting new orders or enquiries.
Support boundaries
- Will support investigate slow PHP or database processes?
- Will it help restore a backup?
- Does it identify plugin issues or stop at “the server is online”?
- Are urgent incidents covered outside office hours?
- Is support direct or passed through a reseller?
Managed WordPress is not a universal specification
“Managed” can mean anything from automatic core updates to a genuinely supported platform with staging, security monitoring and restores. Require a written list of what is managed, what is excluded and who acts when an update breaks the site.
Migration and ownership
The business should be able to download the complete files and database, change DNS, access logs and transfer the site to another compatible host. Proprietary management layers are acceptable only when the exit route is understood.
A practical hosting test
- Create a temporary installation.
- Enable HTTPS and normal permalinks.
- Install only the intended theme and essential plugins.
- Run a backup and restore it to staging.
- Test forms, scheduled tasks and admin responsiveness.
- Ask support one realistic technical question and assess the answer.
Practical next step
Request the host’s current PHP/database versions, resource limits, backup retention, restore process and full exit procedure in writing before committing a production site.
Resource limits matter as much as storage
Large storage allowances can distract from limits on memory, PHP workers, processes, database connections and scheduled tasks. A small shop, membership site or busy form system may exhaust processing limits while using little disk space. Ask how the host reports resource pressure and what evidence is available when the site slows down.
Questions about automatic management
- Are WordPress core updates automatic, and can major releases be delayed for testing?
- Are plugin and theme updates included or merely displayed?
- Does malware cleanup form part of the service, and under what conditions?
- Who checks whether an automatic backup or update actually succeeded?
- Can a failed change be rolled back without replacing newer orders or enquiries?
Do not treat a branded “WordPress hosting” label as evidence. The written answers and a practical restore test are more useful.
Sources and date checked
This guide was checked on 21 July 2026. WordPress, hosting environments and extensions change, so recheck the relevant official documentation before making a major change.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.