Owner tools

For the owner of freispace (Visit site).

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

Email security

MEDIUMConfigure DKIM with your email provider
No DKIM record found at the common selectors we check.
WhyDKIM signs your outbound mail with a cryptographic key receivers can verify. Without it, receivers can't tell your real mail from a spoof.
WhereAsk your email provider for their DKIM setup. It's usually one TXT record at {selector}._domainkey.{your-domain}.
Learn more
Why this matters & sources
Selectors we probe: Resend, SendGrid, Postmark, Mailchimp, Brevo, Mailgun, HubSpot, Customer.io, ConvertKit, Cloudflare Email. If you use Google Workspace, Microsoft 365, or self-hosted email with a custom selector, you may already have DKIM published and we just don't see it.

Page basics & SEO

LOWTrim your meta description to under 160 characters
Currently 245 characters: "Future-proof your post-production studio with freispace: the AI-ready scheduling platform for seamless human-AI collaboration. Optimize workflows, gain a competitive edge, and manage resources efficiently. Get your AI readiness assessment today."
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
14 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

Agent / AI

LOWAdd Link response headers
WhyLets agents discover your sitemap, privacy policy, and docs without parsing HTML, which most lightweight agents skip.
WhereSet Link: response headers in your server config or framework middleware.
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://freispace.com/en-us. StackScope (https://stackscope.dev) analysed it on 4 July 2026 and scored it 10.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:
brevo, bunny-cdn, capterra, cloudflare-dns, google-site-verification, hsts, lemlist, postman, svelte, sveltekit, tailwindcss

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/wktzqd40/freispace

I own https://freispace.com/en-us. StackScope (https://stackscope.dev) analysed it on 4 July 2026 and scored it 10.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):
brevo, bunny-cdn, capterra, cloudflare-dns, google-site-verification, hsts, lemlist, postman, svelte, sveltekit, tailwindcss

Optional best-practice improvements (no score impact):
- [MEDIUM] Configure DKIM with your email provider. No DKIM record found at the common selectors we check. Why: DKIM signs your outbound mail with a cryptographic key receivers can verify. Without it, receivers can't tell your real mail from a spoof. Where: Ask your email provider for their DKIM setup. It's usually one TXT record at `{selector}._domainkey.{your-domain}`. (https://www.cloudflare.com/learning/dns/dns-records/dns-dkim-record/)
- [LOW] Trim your meta description to under 160 characters. Currently 245 characters: "Future-proof your post-production studio with freispace: the AI-ready scheduling platform for seamless human-AI collaboration. Optimize workflows, gain a competitive edge, and manage resources efficiently. Get your AI readiness assessment today." 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 Link response headers. Why: Lets agents discover your sitemap, privacy policy, and docs without parsing HTML, which most lightweight agents skip. Where: Set `Link:` response headers in your server config or framework middleware. (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link)
- [LOW] Serve right-sized images. 14 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)

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/wktzqd40/freispace

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/wktzqd40/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/wktzqd40/freispace"><img src="https://stackscope.dev/badge/wktzqd40/current.svg" alt="StackScope score for freispace" 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/wktzqd40/freispace"><img src="https://stackscope.dev/badge/wktzqd40.svg" alt="StackScope launch score for freispace" 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.