We read the response headers of your public page, tell you which are missing and how much each one matters, and say where to set it on your host. No email needed.
Speed on a phone
Main content
First paint
Speed index
Blocked input
Layout shift
What to fix
Take it with you
Rather hand it over?
Relaunch starts with an audit of your live product, then we fix what holds it back.
Browsers mark the site as not secure and forms send data in the clear
Fix before launch
HTTP to HTTPS redirect
People who type the bare domain should land on the secure version
Fix soon
Strict-Transport-Security
Keeps a returning visitor on HTTPS on a hostile network
Fix soon
Content-Security-Policy
Limits what an injected script can do; a wrong policy can break analytics and embeds
Worth doing later
X-Frame-Options or frame-ancestors
Stops other sites from framing your page
Worth doing later
X-Content-Type-Options
A small hardening step
Worth doing later
Referrer-Policy
Browsers already default to a safe value; this makes it explicit
Worth doing later
We rank them by what they protect on a typical launch page, so a missing CSP on a marketing site does not read like an emergency.
Where to set them
Next.js: in headers() in next.config.
Vercel: in the headers block of vercel.json.
Netlify and Cloudflare: in a _headers file in the folder copied to the site root.
Framer, Webflow, Shopify and Wix: the platform controls headers, so check its settings first.
The result names your stack as we read it and gives the matching line.
What this does not check
We read one public page. Sign-up, payments, your backend, your dependencies and the pages behind a login are not tested, so a clean result is not a full security audit.