Hosting marketing is full of claims about speed, reliability, and support that don't always match reality. Before signing up, there are specific things you can verify and specific questions you should ask. Here's a checklist that cuts through the marketing and focuses on what actually affects your site.
Ask or check what web server the host uses. LiteSpeed is significantly faster than Apache for WordPress workloads, especially for caching and uncached PHP. Apache is adequate but shows its age with high concurrency. Nginx is fast but requires more configuration for WordPress and has no native .htaccess support, making it impractical for most shared hosting environments.
The web server technology affects performance more than most other variables, this isn't marketing, it's measurable. A host running LiteSpeed with LSCache active will consistently deliver lower Time to First Byte than an Apache or plain Nginx setup at the same price point. When a host doesn't advertise their web server, ask before signing up. If they don't know, that's a signal.
Confirm the host supports PHP 8.x and allows you to switch versions per domain. Check what PHP memory limit is provided, 256MB is a reasonable minimum for WordPress, 512MB for WooCommerce. Verify that you can configure PHP settings (memory limit, upload size, execution time) via cPanel's PHP selector or equivalent, rather than submitting support tickets for every adjustment.
Also check whether the host supports PHP-FPM (FastCGI Process Manager). PHP-FPM handles concurrent requests more efficiently than the older mod_php or CGI approaches. On hosts running LiteSpeed, LSAPI replaces PHP-FPM and is faster still. Knowing which execution model your host uses matters if you're running a WooCommerce store or any site with significant dynamic content.
Older PHP versions (7.4 and below) should be a red flag in 2025. They receive no security patches and introduce compatibility issues with modern WordPress plugins. A host that hasn't invested in PHP 8.x support hasn't invested in their infrastructure.
Read the actual backup policy, not the marketing headline. Key questions: how often are backups taken, how many restore points are kept, where are backups stored (same server or offsite), are backups included in the base price or charged as an add-on, and how do you restore from a backup (self-serve via cPanel or support ticket only).
Daily automated backups retained for at least 14 days, stored offsite, with self-serve restoration is the standard you should expect. Weekly backups are insufficient, a site compromised midweek could lose six days of content on restore. Backups stored on the same server as the site are useless in a server-wide failure scenario.
Some hosts sell "CodeGuard" or equivalent backup add-ons as a paid monthly service. If daily backups are behind a paywall, calculate that cost into your total monthly spend. A host that includes it by default is already ahead.
A 99.9% uptime guarantee sounds reassuring, but check the SLA terms carefully. Does the guarantee cover scheduled maintenance? What's the compensation mechanism if they fail to meet it, account credit is typical, but the amount varies widely. A guarantee with meaningful compensation is more credible than a promise with no consequence for non-performance.
Third-party uptime tracking is more reliable than the host's own claims. Search for the host name plus "uptime" on independent review platforms or developer forums. Hosts with consistently strong uptime tend to have that reflected in community reports; those with recurring issues have documented histories that marketing pages won't show you.
99.9% uptime still allows roughly 8.7 hours of downtime per year. 99.95% allows about 4.4 hours. For a transactional site, that distinction matters. Ask whether the SLA excludes "planned maintenance", some hosts define very broad maintenance windows that aren't counted against uptime guarantees.
Support quality is difficult to assess pre-purchase. The best proxy is testing it: submit a technical pre-sales question via live chat or ticket before signing up. Ask something specific, "What PHP execution model do you use on shared plans?" or "Does your LiteSpeed configuration support ESI for partial page caching?" How long does a response take? Is the answer technically accurate and specific, or generic and unhelpful?
Support teams that can answer specific WordPress and server questions are more valuable than those who can only relay information from a knowledge base. Avoid hosts where live chat is 24/7 sales and tickets take 48 hours for technical responses. The pattern of routing technical questions to an email queue with a 24–48 hour SLA while keeping sales chat instant is a tell.
Also verify whether technical support is available 24/7 or only during business hours. Sites don't go down on schedule. A host with genuine 24/7 technical support (not just a billing team) is meaningfully different from one where you can only reach account management outside of UK business hours.
Check whether the host uses NVMe SSD, standard SSD, or spinning HDD storage. NVMe is the current standard for performance hosting, it delivers significantly better random I/O compared to SATA SSDs, which matters for WordPress database performance and file operations. Any host still using HDDs for shared hosting in 2025 is running dated infrastructure.
Inode limits are the hidden constraint on "unlimited storage" plans. An inode is essentially a file or directory on the server. WordPress installations are inode-heavy: themes, plugins, media uploads, and WordPress core files all consume inodes. A plan with 100,000 inodes will limit you to roughly 100,000 files total across your account. For a site with a large media library or multiple WordPress installs, this becomes a real constraint. Ask about it explicitly.
A staging environment lets you test plugin updates, theme changes, and major modifications before pushing them to your live site. This should be a standard feature, not a premium add-on. Confirm whether staging is included on your plan or requires upgrading.
Better staging tools let you push changes from staging to live with a single click and pull the live database back to staging to test with real data. Basic staging tools require manual file and database synchronisation. If you're running a WooCommerce store or any site that updates frequently, the quality of staging tooling directly affects how safely you can maintain the site.
The introductory price on most hosting plans is significantly lower than the renewal price. A plan advertised at £1.99/month renews at £9.99/month. Check the renewal price explicitly before signing up, and calculate your total cost over the first two years rather than just the initial term. Hosts with transparent, stable pricing are preferable to those that use loss-leader introductory offers to lock in customers before a significant price increase.
The maths is simple: a host charging £5/month with no promotional rate is cheaper over two years than one charging £1.99 for year one and £9.99 at renewal. Add in migration costs (time and possibly a developer fee) if you want to move after year one and the economics of chasing the cheapest introductory rate become even less attractive.
HostBible plans include LiteSpeed, daily backups, PHP 8.x, NVMe storage, staging, and support that can actually answer WordPress questions. No bait-and-switch renewal pricing.
View Hosting Plans