Grav Benchmarks

Developers and small teams wanting a lightweight CMS for brochure sites, docs, or small publications.

A small content website or documentation site.

• Grav sites are built by developers who chose flat-file specifically. Performance is intentionally high -- no database queries, no plugin overhead, no framework weight.
• Documentation and developer blogging are the dominant use cases. Content is technical, well-organized, and frequently updated.
• Version control integration is typically present. Grav's file-based architecture makes git-backed content management practical.

• Documentation sites with strong technical content but weak commercial conversion. Great resource; no reason to act.
• Missing business identity schema -- Grav is developer/content focused and doesn't prompt for Organization or LocalBusiness context.
• Thin corpus sample makes broad generalizations harder. Grav is a small platform with a very specific audience.

• Grav sites have near-zero third-party script adoption compared to database-driven CMSs in our corpus. The minimal dependency philosophy extends to the entire tech stack -- not just the CMS.
• Grav sites show the highest rate of version-controlled content patterns in our corpus. The flat-file architecture makes git-backed workflows practical, and the developer audience uses them.