Test the hardest page first
Do not evaluate either platform only with a polished homepage. Build a representative article, a long service page and the most complicated content relationship. Ask the future editor to replace an image, add an entry and preview the result.
Write down the operational requirements
List languages, editor roles, content collections, forms, redirects and integrations. Check the current plan documentation for each requirement before buying. Separate features that work within the platform from those requiring a third-party subscription or custom code.
Choose a maintenance model
A visual tool does not eliminate design or publishing decisions. Decide who owns the site after handover and what changes they can make safely. Compare the total annual operating cost and the export or migration path, not just the initial build speed.
Sources & further reading
Public sources consulted for this edition. Agency descriptions reflect published offerings, not an independent performance audit.
How we publish these guides →