Review site hosting where every rating is counted once.
A review site is a publishing site with a write queue bolted on. The reading is cacheable and the writing is not, and the average score sitting on the page is what breaks when those two are configured as if they were the same thing.
Everything a ratings site asks of a host.
Reviews arrive in bursts, are read thousands of times each, and change a number that is printed on every page they touch. Each of those is a different problem.
Aggregates that do not run on the request
Recomputing an average over every review of a product while a visitor waits is the classic review-site stall. The recalculation is moved to a background job and the stored value is what pages read.
Submission endpoints excluded from cache
The form that accepts a review, the endpoint that records a helpful vote and the nonce that protects both are dynamic by definition. They are excluded from the page cache rather than fighting it.
Spam rejected before WordPress loads
Review forms attract automated submissions at a volume unrelated to your real traffic. Rate limiting happens at the edge, so a flood costs bandwidth rather than PHP workers.
Moderation queues that drain on schedule
Pending reviews, notification emails and reminder digests are scheduled work. Platform cron runs them at the time they are set for rather than when the next visitor happens to arrive.
Structured data that survives the cache
Rating markup is generated with the page, so a cached page carries the score it was built with. Purging on a new review is what keeps the markup and the number in agreement.
Staging for scoring changes
Changing how a score is weighted rewrites numbers across the whole site. Do it on a clone, compare the output, then push it.
Watch the queue, not just the traffic.
On a review site the interesting metric is not visitors. It is how many submissions are waiting, how long the aggregate job took, and whether the last purge covered every page the score appears on.
- 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 product page with four hundred reviews.
The page is cacheable. What decides whether it can be built at all is how the reviews are counted and how they are paginated, and both are configuration rather than content.
What we change for a review site
These differ from a standard WordPress site on the same plan, and each one follows from the same fact: the number on the page is derived from rows that keep arriving.
| Setting | What we do | Why |
|---|---|---|
| Rating aggregates | Stored and recalculated by a background job rather than summed on read | An average computed across every review row on each page view gets slower with every review the site succeeds in collecting, which turns popularity into a performance problem. |
| Cache purging | Scoped to the pages a new review changes, including listings and category rollups | A score printed on a product page also appears in listings and top-rated widgets, so purging only the product leaves the same review showing two different averages. |
| Submission endpoints | Excluded from the page cache and from bot challenges | A cached submission form serves a stale nonce, which rejects the review and reads to the visitor as the site being broken. |
| Edge rate limiting | Applied to review and vote endpoints specifically | Automated submissions target the form rather than the site, so a limit that protects everything equally either throttles readers or lets the flood through. |
| Review pagination | Server-side, with comment splitting enabled | Rendering hundreds of reviews into one response spends memory on markup nobody scrolls to, and it is the memory limit rather than the query that fails first. |
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.
Why do my average ratings sometimes look wrong?
Can the site handle a few hundred reviews on one product?
How do you handle spam review submissions?
Will the rating markup in search results stay accurate?
Can I change how scores are weighted without breaking the site?
Collect the reviews without slowing down the page.
Start in minutes, or let our team move your review site across - no card, no commitment.