Quiz hosting for traffic that writes on every visit.
A quiz visitor does not read a page, they submit to it, several times over. That inverts the read-heavy assumption every default WordPress setup is built on.
Everything a quiz asks of a host.
Every question answered is a write, every result is a row, and a quiz that gets shared brings all of them at once.
Answer writes that do not queue
Question-by-question submissions hit the database far more often than ordinary traffic ever does, so connection pooling and write capacity are sized for that pattern rather than for page views.
Ready for a quiz that gets shared
Quizzes spread in bursts, and the burst consists of people taking the quiz rather than reading about it, so the capacity that matters is submission throughput.
An attempts table that stays fast
Results accumulate forever and are queried back for leaderboards and reporting, so the table is indexed and partitioned by date rather than left to grow without limit.
Answers that stay the taker's
Submission and result URLs bypass the cache entirely, so nobody is ever shown a score page that was generated for somebody else.
Scoring that finishes under load
Score calculation and result generation run with limits sized for the longest quiz on the site rather than a default that quietly assumes ten questions.
See attempts, not just visits.
A quiz site's health is measured in completed attempts. Page views tell you people arrived; attempts tell you the writes are landing.
- Attempt and completion rates
- Storage view as results accumulate
- One-click admin login
- Restore any daily backup from the dashboard
A submission during a viral hour.
Reads can be cached and writes cannot, which means a quiz site's ceiling is decided entirely by how many simultaneous writes the database will accept.
What we change for a quiz site
These are the settings that differ from a standard WordPress site on the same plan. Each follows from a visitor generating writes rather than reads.
| Setting | What we do | Why |
|---|---|---|
| Database connection pool | Sized for sustained concurrent writes | A quiz taker generates a write per question, so a pool tuned for read traffic saturates at a fraction of the visitor count you expected. |
| Full-page cache | Bypassed on submit, scoring and result URLs | A cached result page shows one taker the score belonging to whoever loaded it first. |
| Attempt storage | Indexed and partitioned by date | Attempt rows accumulate without limit and are read back for leaderboards, which turns an unindexed table into the slowest query on the site. |
| Scoring execution limits | Set from the longest quiz on the site | Default execution time assumes a short form, and a hundred-question assessment with weighted scoring is not a short form. |
| Submission endpoints | Isolated with their own rate limits | A quiz that gets shared sends every one of those visitors to the same endpoint within the same few minutes. |
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.
Will results be mixed up between people?
What happens if a quiz goes viral?
Where are past attempts stored?
Can I run long assessments?
Do you support quiz plugins?
Move your quiz site to a host that expects the writes.
Free migration, submissions that land, and an attempts table that stays fast.