Owner tools

For the owner of Velacare (velacare.app).

Ownership

This launch is unclaimed.

Claim this launch to get an owner link, re-scan after fixes, track your score improvements, or remove your site from StackScope entirely.

Claim this launch

Optional improvements

These don't change your StackScope score but cover SEO, agent-readiness, security-researcher discoverability, and compliance items worth addressing.

Security

LOWAdd /.well-known/security.txt
WhyLets security researchers report vulnerabilities responsibly through a published contact channel.
WhereCreate /.well-known/security.txt with a Contact: email and Expires: date.
Learn more

Legal & compliance

HIGHGate analytics behind consent
Analytics set tracking cookies on our visit with no opt-in step. If you gate this for real visitors in a way our crawl didn't trigger, you can ignore it.
WhyUK/EU GDPR requires opt-in before analytics scripts fire; about half of US state privacy laws now require honouring the Global Privacy Control browser signal as a universal opt-out.
WhereDrop in Cookiebot, Usercentrics, Osano, or Iubenda Consent, or hand-roll a banner plus Google's Consent Mode v2.
Learn more
Why this matters & sources
The legal landscape: UK/EU GDPR treats analytics as personal-data processing that requires opt-in consent before scripts fire. About half the US state privacy laws now in force (California, Colorado, Texas, Connecticut, Oregon, Montana, Delaware, New Hampshire, New Jersey, Nebraska) require honouring the Global Privacy Control (GPC) browser signal as a universal opt-out, and California's January 2026 regulations require visibly indicating when a GPC signal has been honoured.
Sources: IAPP US state privacy tracker (iapp.org/resources/article/us-state-privacy-legislation-tracker), California AG on GPC (oag.ca.gov/privacy/ccpa/gpc), EDPB consent guidelines (edpb.europa.eu).

Email security

HIGHAdd an SPF record
No SPF TXT record found at the apex domain.
WhyWithout SPF and DMARC, receiving servers have fewer signals to reject spoofed mail using your domain.
WherePublish a TXT record at the apex like v=spf1 include:_spf.google.com ~all (replace the include: with your real sender, then end with ~all for soft-fail or -all for strict).
Learn more
MEDIUMMove DMARC from p=none to quarantine or reject
DMARC policy is p=none (monitoring only).
Whyp=none lets receivers log failures but still deliver spoofed mail. Real protection only kicks in at quarantine or reject.
WhereAfter reviewing a few weeks of rua= reports and confirming your real senders pass, change to p=quarantine (sends spoofs to spam) and then p=reject (blocks them outright).
Learn more
LOWAdd MTA-STS
No MTA-STS DNS record published.
WhyPrevents mail to your domain being downgraded to plaintext mid-flight by a network attacker. Most launches don't have this, so deploying it puts you a tier above generic email-security checks.
WherePublish a TXT record at _mta-sts.{your-domain} plus a policy file at https://mta-sts.{your-domain}/.well-known/mta-sts.txt.
Learn more
LOWAdd a TLS-RPT record
No TLS-RPT record at _smtp._tls.{domain}.
WhyReceivers can tell you when STARTTLS handshakes to your mail server fail. Without it, silent TLS failures are invisible.
WherePublish one TXT record at _smtp._tls.{your-domain} like v=TLSRPTv1; rua=mailto:[email protected].
Learn more

Page basics & SEO

LOWTrim your meta description to under 160 characters
Currently 171 characters: "Upload your dog's blood work PDFs and instantly see how their biomarkers trend over time. Track liver, kidney, CBC, thyroid, and metabolic values with clear visual charts."
WhyGoogle truncates around 155-160 characters on desktop SERPs (less on mobile), so anything past that won't appear in the snippet.
WhereEdit your <meta name="description"> tag. Put the most click-worthy phrase first.
Learn more

Performance

LOWServe right-sized images
2 images are downloaded at more than twice the displayed size.
WhyShipping a 2000px image into a 400px slot wastes bandwidth and slows loading, especially on mobile.
WhereResize to the displayed dimensions, or use srcset/sizes (or a framework image component) to serve per-viewport variants.
Learn more
LOWAdd alt text to your images
3 images have no alt attribute.
WhyScreen-reader users get no description, and search engines lose a signal about the image content.
WhereAdd a concise alt="..." to each image (an empty alt="" is correct only for purely decorative images).
Learn more

If a tip looks wrong (for example it says "add a consent banner" and you already have one) the detection's the bug, not you. StackScope sees what's public from the outside: HTTP response, rendered HTML, cookies, and DNS. We can miss vendors that load behind consent, are self-hosted, or use an install shape we haven't fingerprinted yet. Email [email protected] and we'll look into it.

Copy into Cursor, Claude, or ChatGPT

This prompt includes the detected stack and only the fixes StackScope found. It asks the AI to make concrete file-level changes, not a vague website review.

Score-affecting basics only. Ask your AI to handle these first; come back for the optional hardening once they're done.

Everything: score-affecting fixes plus optional email security, agent metadata, and best-practice items. Longer prompt, more for an "all in one" agent run.

I own https://velacare.app. StackScope (https://stackscope.dev) analysed it on 16 June 2026 and scored it 9.0/10 against their production-readiness checklist. Nothing score-affecting is currently outstanding, so use this prompt as a posture check rather than a fix list.

Tech stack StackScope detected on the site:
authjs, google-site-verification, hsts, mixpanel, nextjs, react, sendgrid, stripe, tailwindcss, vercel, vercel-dns

Spot-check the stack above against current best practices: anything that looks deprecated, mis-configured, or like drift since the last deploy. If everything looks healthy, say so. Don't invent issues to fill the response.

Full analysis: https://stackscope.dev/launch/5850or9e/velacare

I own https://velacare.app. StackScope (https://stackscope.dev) analysed it on 16 June 2026 and scored it 9.0/10 against their production-readiness checklist. Please help me apply the fixes below. This is a checklist, not a blocker list; Score-affecting fixes are the ones that move the number, Optional items are nice-to-haves with zero score impact that I can skip for an MVP.

Tech stack StackScope detected on the site (use this when suggesting where each fix lives in the codebase):
authjs, google-site-verification, hsts, mixpanel, nextjs, react, sendgrid, stripe, tailwindcss, vercel, vercel-dns

Optional best-practice improvements (no score impact):
- [HIGH] Gate analytics behind consent. Analytics set tracking cookies on our visit with no opt-in step. If you gate this for real visitors in a way our crawl didn't trigger, you can ignore it. Why: UK/EU GDPR requires opt-in before analytics scripts fire; about half of US state privacy laws now require honouring the Global Privacy Control browser signal as a universal opt-out. Where: Drop in Cookiebot, Usercentrics, Osano, or Iubenda Consent, or hand-roll a banner plus Google's `Consent Mode v2`. (https://iapp.org/resources/article/us-state-privacy-legislation-tracker)
- [HIGH] Add an SPF record. No SPF TXT record found at the apex domain. Why: Without SPF and DMARC, receiving servers have fewer signals to reject spoofed mail using your domain. Where: Publish a TXT record at the apex like `v=spf1 include:_spf.google.com ~all` (replace the `include:` with your real sender, then end with `~all` for soft-fail or `-all` for strict). (https://www.cloudflare.com/learning/dns/dns-records/dns-spf-record/)
- [MEDIUM] Move DMARC from p=none to quarantine or reject. DMARC policy is `p=none` (monitoring only). Why: p=none lets receivers log failures but still deliver spoofed mail. Real protection only kicks in at quarantine or reject. Where: After reviewing a few weeks of `rua=` reports and confirming your real senders pass, change to `p=quarantine` (sends spoofs to spam) and then `p=reject` (blocks them outright). (https://dmarc.org/overview/)
- [LOW] Trim your meta description to under 160 characters. Currently 171 characters: "Upload your dog's blood work PDFs and instantly see how their biomarkers trend over time. Track liver, kidney, CBC, thyroid, and metabolic values with clear visual charts." Why: Google truncates around 155-160 characters on desktop SERPs (less on mobile), so anything past that won't appear in the snippet. Where: Edit your `<meta name="description">` tag. Put the most click-worthy phrase first. (https://developers.google.com/search/docs/appearance/snippet)
- [LOW] Add /.well-known/security.txt. Why: Lets security researchers report vulnerabilities responsibly through a published contact channel. Where: Create `/.well-known/security.txt` with a `Contact:` email and `Expires:` date. (https://securitytxt.org/)
- [LOW] Add MTA-STS. No MTA-STS DNS record published. Why: Prevents mail to your domain being downgraded to plaintext mid-flight by a network attacker. Most launches don't have this, so deploying it puts you a tier above generic email-security checks. Where: Publish a TXT record at `_mta-sts.{your-domain}` plus a policy file at `https://mta-sts.{your-domain}/.well-known/mta-sts.txt`. (https://datatracker.ietf.org/doc/html/rfc8461)
- [LOW] Add a TLS-RPT record. No TLS-RPT record at `_smtp._tls.{domain}`. Why: Receivers can tell you when STARTTLS handshakes to your mail server fail. Without it, silent TLS failures are invisible. Where: Publish one TXT record at `_smtp._tls.{your-domain}` like `v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com`. (https://datatracker.ietf.org/doc/html/rfc8460)
- [LOW] Serve right-sized images. 2 images are downloaded at more than twice the displayed size. Why: Shipping a 2000px image into a 400px slot wastes bandwidth and slows loading, especially on mobile. Where: Resize to the displayed dimensions, or use `srcset`/`sizes` (or a framework image component) to serve per-viewport variants. (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#srcset)
- [LOW] Add alt text to your images. 3 images have no alt attribute. Why: Screen-reader users get no description, and search engines lose a signal about the image content. Where: Add a concise `alt="..."` to each image (an empty `alt=""` is correct only for purely decorative images). (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#alt)

For each item, tell me exactly which file to create or which code to change, and where it lives in a project using the stack above. If my framework has a native API for the task (e.g. Next.js metadata exports, `app/sitemap.ts`, Astro layouts, Nuxt `useHead`), prefer that over raw HTML or server config.

Full analysis: https://stackscope.dev/launch/5850or9e/velacare

Using an autonomous agent?

Point the agent at this SKILL.md URL and ask it to follow the skill. The framing stops agents defaulting to an open-ended page review.

https://stackscope.dev/launch/5850or9e/skill.md

Share your score

Your score card renders automatically when you share the link.

Or embed a badge

Two badge options. Pick whichever fits your story.

Current score

Shows the latest score and updates within a few minutes of any recrawl. Best for ongoing display: if you fix something and recrawl, the badge reflects the new score automatically.

<a href="https://stackscope.dev/launch/5850or9e/velacare"><img src="https://stackscope.dev/badge/5850or9e/current.svg" alt="StackScope score for Velacare" height="24" /></a>

Launch score

Pinned to your launch-day snapshot and never changes. Marked with a small gold corner ribbon. Best for press kits, launch retrospectives, or anywhere you want a permanent record of how you shipped.

<a href="https://stackscope.dev/launch/5850or9e/velacare"><img src="https://stackscope.dev/badge/5850or9e.svg" alt="StackScope launch score for Velacare" height="24" /></a>

Using a Content-Security-Policy? Both badges are <img> tags from our domain, so your CSP needs to allow them. Add stackscope.dev to your img-src directive (example: img-src 'self' stackscope.dev;). Without it, browsers silently block the badge and visitors see a broken image.