Performance Optimization

Every site ships as static HTML with no client-side framework runtime — see Key Concepts for why. That foundation rules out the biggest performance killer before you've touched a setting: there's no framework bundle to ship, hydrate, or optimize.

Run the SEO & AI Audit from a site's dashboard for a Lighthouse-based check. For Core Web Vitals specifically, aim for LCP under 2.5s, INP under 200ms, and CLS under 0.1 — Google's published thresholds for "good." Pro and above also get first-party Core Web Vitals tracking on the live site itself, adding at most a few extra beacons per page load.

Every upload gets converted to WebP and gets a set of responsive size variants generated alongside it, served from Zitegen's CDN. You still control the input: upload a reasonably-sized original rather than a multi-megabyte camera file, and write real alt text — that part isn't automated.

A video never eagerly downloads its full source on page load — only its metadata, until a visitor presses play. Uploads also get a poster frame captured automatically, so the page shows a real thumbnail instead of a black box while the video is still loading.

A site has exactly two font slots — heading and body — set site-wide, not per section. There's no way to sprinkle in a third or fourth typeface even if you wanted to; the constraint that keeps font-loading cheap is structural, not a guideline to remember. See Typography for how fonts are chosen and self-hosted.

Anything wired up in Site Settings — analytics, chat widgets, CRM snippets — renders straight into the compiled page. Each one is a real request, so add only what you'll actually use. Tracking snippets are consent-gated behind the cookie banner automatically whenever any tracking integration is connected, so they don't fire before a visitor accepts.