Sanity Benchmarks

Developer led teams managing content across websites, apps, and multiple digital channels.

Headless marketing website.

• Sanity-backed sites are API-first -- what Stackra scans is the frontend framework (Next.js, Remix, Astro), not Sanity itself. Performance depends entirely on the frontend choice.
• Schema diversity is higher on Sanity-backed sites than any other CMS. Because schema is explicitly coded rather than auto-generated by a plugin, it's more varied and more intentional.
• Content consistency across types is a Sanity strength. Well-modeled content produces well-structured metadata -- the discipline of the CMS shows in the output.

• Image optimization is entirely frontend-dependent. Sanity stores the source; the pipeline is the developer's problem.
• Schema adoption is better in theory than practice. Headless architecture means no plugin auto-generates it -- someone has to build it.
• Runtime performance depends entirely on the frontend framework choice and how it was deployed. Sanity sites have the widest performance variance in our corpus.

• Sanity-backed sites show the highest schema diversity of any CMS in our corpus. Schema built by hand rather than generated by a plugin is more varied, more intentional, and more likely to be entity-appropriate.
• Sanity sites show the widest performance variance in our corpus. Two Sanity sites can differ by 60+ Lighthouse points -- a direct reflection of the frontend-choice architecture where the CMS and the renderer are separate decisions.