BizruptOverview →
All sites

Webflow CMS · Pre-launch / Domain issue

lumamind.io

Functionally broken in production. Only 4 URLs in sitemap (homepage, contact, privacy, terms), 6 KB homepage, no nav, no analytics, apex domain (`lumamind.io`) failing TLS/DNS. Lighthouse desktop fails with `NO_FCP` (the page never paints); real-user verification confirms the site times out on load. The Webflow JS bundle is doing 25 s of blocking work to render nothing. Sunset or replace with a static coming-soon page.

Domain Rating
0.2
Organic traffic
0/mo
Referring domains
0
PSI mobile
46
PSI desktop
n/a
SEO·CriticalTech·CriticalPerf·CriticalContent·CriticalAnalytics·Critical

Snapshot#

  • The site does not load reliably in production. Verified independently: real-user load attempts time out before the page paints, and Lighthouse's desktop run fails with NO_FCP (no First Contentful Paint observed in budget). On mobile Lighthouse reports 25.4 s of Total Blocking Time and 39 s of main-thread work — the Webflow JS bundle is consuming nearly forty seconds of CPU to render a 6 KB stub. This is the single worst-performing page in the portfolio by an order of magnitude, despite having the least content.
  • Apex domain fails to respond. https://lumamind.io/ returns no response (TLS or DNS misconfiguration). Only https://www.lumamind.io/ resolves with a 200. This matches the "Update domains" warning visible in the Webflow workspace.
  • Site is effectively a 4-page placeholder. Sitemap lists only /, /contact, /privacy, /terms. No services, no team, no programs, no blog.
  • Homepage HTML is 6.4 KB. The HTML is tiny; what fails is everything Webflow ships around it — jQuery, the runtime JS bundle, fonts, and animation logic for the split-letter H1.
  • No analytics anywhere. No GTM, no GA4, no CallRail, no Meta pixel.
  • Same Webflow technical defaults as the rest of the portfolio: empty robots, no canonical, no meta description, no schema, no Open Graph.
  • No clear positioning. Title is just "Luma Mind", H1 begins "Luma…", nav has a single /contact link.

Bottom line: the site is broken, not just incomplete. Today it serves a worse user experience than a blank document. Pick one of three exits this week — (a) replace the page with a static one-paragraph "coming soon" + email capture (1 hour of work), (b) park the domain with a 302 to whichever portfolio site is the closest fit, or (c) release the registration. Anything that keeps the current Webflow build live is actively damaging brand trust for visitors who land on it from a backlink, a card, or a direct entry.

Site basics#

  • Primary domain: lumamind.io (apex broken) → use www.lumamind.io
  • Hosting / CMS: Webflow CMS plan
  • Stack notes: Webflow JS, jQuery. No analytics in HTML.
  • Information architecture (per sitemap and Ahrefs crawl, 2026-05-13): /, /contact, /privacy, /terms. That's the entire site. Ahrefs has crawled exactly these 4 URLs and zero others.
  • Webflow workspace flag: "Update domains" visible in the agency dashboard.

SEO#

The Ahrefs check below exists to confirm there is no organic footprint to protect before any domain decision is made.

Headline metrics (Ahrefs, 2026-05-13)#

Metric Value
Domain Rating 0.2
Organic traffic (US, monthly) 0
Organic keywords 0
Live backlinks 0
Live referring domains 0
All-time referring domains 1

Confirmed: there is no SEO equity to preserve. Any decision (rebuild, park, sunset) is free from an SEO standpoint.

Technical SEO#

Critical issues (verified live)#

  • Apex domain lumamind.io returns no response. TLS/DNS misconfiguration. Either point apex via A/ALIAS to Webflow's IPs and provision the cert, or remove the apex from any marketing materials.
  • /robots.txt returns Webflow's 404 HTML on the www subdomain.
  • No meta description.
  • No canonical tag.
  • No Open Graph tags at all.
  • No JSON-LD / schema.
  • Title is just Luma Mind. No qualifier, no positioning.
  • H1 is a single word "Luma…" wrapped in animation transform CSS. Likely a scripted reveal that splits the H1 across multiple DOM nodes. Hurts accessibility and crawlability.
  • Zero H2s.

Existing (limited) strengths#

  • A sitemap.xml at the apex does exist (4 URLs).
  • HTTPS works on the www subdomain.

Per-page audit (live crawl, 2026-05-13 — entire site, 4 pages)#

Page HTTP Title Meta desc H1 Canonical Schema
/ 200 "Luma Mind" (9 chars) "Luma" (animated split, no terminating "Mind")
/contact 200 "Contact" "Contact us"
/privacy 200 "Privacy Policy" "Privacy Policy for LumaMind"
/terms 200 "Terms of Service" "Terms of Service for LumaMind"

Confirms the snapshot: every page on the entire site is missing meta description, canonical, and schema, and the homepage H1 doesn't even contain the brand name.

Performance & Core Web Vitals#

Source: PageSpeed Insights API (Lighthouse 12, lab data), https://www.lumamind.io/, 2026-05-13. The result is surprising in a bad way.

Mobile#

Audit Score Notes
Performance 46 Red — astonishing for a 4-page placeholder
Accessibility 89 Orange
Best Practices 100 Green
SEO 90 Green
Core Web Vital Lab value Threshold Verdict
LCP 3.4 s ≤ 2.5 s 🟠
FCP 3.4 s ≤ 1.8 s 🟠
TBT 25,440 ms ≤ 200 ms 🔴 The site does 25 seconds of blocking JavaScript work to render a 6 KB stub page
CLS 0 ≤ 0.1 🟢
Main-thread work — — 🔴 39.4 s total CPU time on Lighthouse's mobile profile

Desktop#

Lighthouse failed with NO_FCP — "The page did not paint any content." The desktop emulator rendered the page and recorded zero First Contentful Paint inside the budget. This is itself a critical signal — the page is so JS-heavy relative to its content that on some viewport conditions it never visibly paints.

Read#

The placeholder ships full Webflow JS, jQuery, and the page's animated H1 ("Luma…") — none of which is needed for a four-page stub. The site has 25 s of total blocking time and 39 s of main-thread work on a phone profile. Until lumaMind is either replaced with a simple coming-soon page or built out into a real site, it is actively a worse user experience than serving a blank document. This reinforces the "decide explicitly: build, park, or sunset" recommendation in the snapshot.

Content & UX#

The site has no meaningful content beyond a hero and a contact link. There is nothing to audit. The most useful UX recommendation is to either:

  • Replace the current page with an explicit "coming soon" with a working email capture, or
  • Sunset the domain and redirect to whichever portfolio site is its closest fit.

Competitive positioning#

Not applicable until positioning is defined. Before building this out, answer:

  • What is lumaMind for? (Brand? Sub-service? Mental-health-specific vs addiction-specific?)
  • Which audience does it target that the existing 4 sites don't?
  • Is the .io TLD intentional, or is .com available?

Analytics & conversion tracking#

  • Nothing installed. Not worth installing until the site's purpose is defined.

Prioritized recommendations#

# Recommendation Impact Effort Owner
1 Decide: build out, park, or sunset. Document the decision. Critical Low Tarzana exec
2 Fix apex DNS/TLS so https://lumamind.io resolves (or remove apex from marketing) High Low DevOps
3 If keeping: replace placeholder with a real positioning page + email capture High Med Design + content
4 If keeping: apply the portfolio-wide technical-SEO fix set (sitemap, robots, meta, schema, OG) Med Low Webflow dev
5 If keeping: install GTM + GA4 + Search Console Med Low Analytics

Audit conducted by Bizrupt. Raw data exports under content/assets/lumamind/.

All sitesCross-portfolio overview