CMS
Remix audit: headers() on the document, not a SPA costume
· Configuration notes, not a newsroom.
SiteRune fingerprints __remixContext. Remix can send headers from the document request. The brief treats it as a server.
Loaders are the origin
Slow TTFB is often a loader that hits the CMS on every anonymous document request with no cache. Cache the document at the CDN. Do not put cookies() equivalent on the marketing layout.
headers export
Security headers belong on the Remix headers() export or the proxy. llms.txt is a resource route. We do not generate a next.config snippet for Remix. If you deployed to Vercel we will say so only when x-vercel-* is present.
Run it on a live URL
The brief will name your CMS and attach the files. Three guest scans, no card.