Comparison site hosting sized for the import, not the page.
The pages are simple. What decides whether a comparison site works is the job that refreshes a few thousand prices overnight and the URL space that filtering creates during the day.
Everything a comparison table asks of a host.
Two workloads share one site: a scheduled write job with no visitors, and a read pattern that generates far more URLs than you have pages.
Imports that survive being interrupted
Price and spec feeds are processed in chunks with the position recorded, so a run that hits a limit resumes where it stopped rather than starting again or importing a row twice.
Outbound lookups with a timeout that exists
A partner API that stops answering should slow one panel, not the page. Outbound requests get an explicit timeout and their responses are cached, so a slow supplier is not your slow site.
Filtered views cached by an allowlist
Filter combinations are effectively unbounded. Known parameters are cached and everything else is normalised away, so the cache stores your real pages rather than a long tail nobody requests twice.
Spec tables paginated server-side
A comparison table with hundreds of rows is a memory problem before it is a rendering one. Pagination happens in the query rather than in the browser.
Refresh runs at a time you choose
Platform cron runs the nightly refresh at the hour it is set for, whether or not anybody is browsing, which is what keeps prices from being a day behind.
Staging for feed format changes
A supplier changing a column name is the usual cause of a bad import. Run the new feed against a clone and compare before it touches live data.
The import is the thing to watch.
A comparison site rarely fails in public. It fails at four in the morning, quietly, and the first symptom is a price that has been wrong for two days.
- One-click admin login, no shared passwords
- Per-site resource and storage view
- Plugin and core updates with per-item status
- Restore any daily backup from the dashboard
A filtered comparison, served from cache.
Filtering is where a comparison site either scales or does not. The difference is whether the cache recognises the URL it is being asked for.
What we change for a comparison site
These differ from a standard WordPress site on the same plan, and each follows from a site whose content is imported rather than written.
| Setting | What we do | Why |
|---|---|---|
| Import execution limits | Raised for the cron context only, not for web requests | A feed run needs minutes while a page request should never take them, and raising both to suit the import removes the limit that stops a runaway page. |
| Import checkpointing | Row position recorded so an interrupted run resumes | A feed that restarts from the beginning after every failure either never completes or writes the same rows twice, and both look identical from the front end. |
| Query parameter handling | Allowlisted parameters cached, unknown ones stripped before the cache key is built | Filter combinations are unbounded, so caching every distinct URL fills the cache with entries requested once and evicts the pages people actually load. |
| Outbound HTTP timeout | Explicit and short, with responses cached | WordPress will wait a long time for a partner API by default, and a supplier having a bad afternoon becomes your page load time. |
| Comparison tables | Paginated in the query rather than rendered whole | A few hundred rows of markup exhausts the memory limit before the database notices the query, so the failure arrives as a blank page rather than a slow one. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
My nightly price import keeps stopping halfway. Why?
Should every filter combination be cached?
What happens when a supplier's API goes down?
How large a catalogue can it handle?
Can I test a new feed format safely?
Keep the prices current and the pages quick.
Start in minutes, or let our team move your comparison site across - no card, no commitment.