Lacuna scores 76/100 as a browser-based AI music toolkit with unusually broad creation-to-editing capability. Its strongest measured areas are technical SEO, risk and stability, and accessibility, while public documentation and buyer decision support remain the most material weaknesses.
Reviewed by SiteList Engine · 12 of 13 dimensions · published Reviewed on October 24, 2026
Is this your site?
Claim itLacuna is a web-based AI music toolkit for creating songs and instrumentals, writing lyrics, editing and enhancing audio, working with stems and MIDI, and turning tracks into shareable visuals.
| Fact | Value |
|---|---|
| Domain | lacuna.fm |
| Category | AI music creation and browser-based audio production |
| Pricing | SaaS subscription with monthly credits, annual plans and non-expiring credit packs |
| Pages crawled | 40 |
| Crawl date | 2026-10-17 |
Lacuna's 76/100 score reflects a capable product surface with a stronger technical foundation than its buyer guidance. The clearest strengths are technical SEO at 95.5/100, risk and stability at 95/100, accessibility at 94/100, and usability at 86.3/100. The site makes AI music creation legible and shows a broad path from creation to editing.
The weaker areas are more commercial and editorial. First impressions and positioning score 61/100, audience and messaging 62/100, and decision-support surfaces 68/100, so visitors must do more work to understand the primary user and compare options. Editorial QA scores 66/100, with the supplied summary pointing to claim support, repeated template language, and mechanical hygiene. Docs and self-serve help are the clearest gap at 34/100: the crawl records a strong machine-readable product inventory and useful homepage FAQ, but insufficient public documentation.
Performance is broadly strong at 78.3/100, with field LCP at 1,986 ms and CLS at 0.03, but mobile p75 INP is 506 ms and falls in the poor band.
Lacuna is immediately legible as AI music creation, but its first screen does not name a primary buyer or surface its strongest differentiator. The H1, "AI Music Generator — Turn a Spark into Sound," and the promise to create, edit, enhance, and share audio establish the category quickly. The more ownable idea appears later in the FAQ: the first song is a connected canvas that supports section editing, stem separation, mastering, and licensing. That claim should move into the hero with one concrete edit example. The supplied crawl shows broad capability explanations and a support contact, but no attributable customer outcome or named comparison. Add an audience qualifier, then pair the connected-canvas promise with verified creator proof.
Lacuna answers "what is this?" quickly, but visitors must infer which music maker it serves first. The hero names an AI music generator and the navigation exposes Music, Lyrics, Stems, and MIDI, while the FAQ explains vocals, genres, free credits, account requirements, commercial rights, and the editing loop. That makes the product mental model stronger than the opening positioning. The unresolved questions are commitment questions: the supplied evidence does not provide concrete cancellation, failure-resolution, or service-level guidance, and it includes no attributable creator result or third-party review artifact. Name one primary creator segment in the hero, surface the create-to-revise loop earlier, and add a compact block covering plan limits, support expectations, and what happens when a generation misses the brief.
Lacuna is easy to understand and compare, but starting creation is framed less clearly than buying a plan. Pricing is one click away through "Pricing" or "View Plans" and presents Basic at $9.50, Pro at $24.50, and Ultra at $49.50 with monthly/yearly context. The homepage inventory contains 39 outgoing links, so the broad tool directory can compete with the core creation path after the focused hero. The main conversion leak is the absence of an explicit "Start free," "Try," or "Sign up" label; the simulated ledger recorded 9 runs, with 6 clean completions and 3 completions with struggle. Add a prominent creation CTA and one recommended workflow, while retaining the plan route for visitors ready to compare.
Lacuna has a strong semantic baseline, but two homepage issues need direct remediation. The sampled homepage, pricing page, and locale routes expose header, navigation, main, and footer landmarks; heading sequences are structured, declared languages match the locale paths, and no positive tabindex values or missing-alt candidates were reported in the sampled accessibility checks. A broader crawler/image inventory separately found missing alt attributes on many pages, so the two findings have different scopes. PSI nevertheless reports a label-content-name-mismatch and a color-contrast failure on the homepage. The supplied artifacts do not identify the exact controls or color pairs, so those details should be retrieved before changing tokens. Reconcile each affected programmatic name with its visible label, correct the measured foreground/background pairs to WCAG AA, then run keyboard and axe checks on the browser workspace and creation controls.
Lacuna’s hierarchy is polished, but small mobile controls and an oversized spacer weaken execution details. The homepage presents one dominant H1, a clear hero, consistent typography, and a readable pricing comparison with Pro highlighted without hiding Basic or Ultra. At 390px, the supplied layout facts report no horizontal overflow, 16px body text, and 18px paragraph text. Three observed mobile controls measure 135x40px, 40x32px, and 36x36px, below the 44px minimum hit area. CSS extraction also reports 191 colors, 36 font sizes, 46 radii, and 36 spacing values, including unused/library rules. Raise the controls, measure the exact PSI failures, reduce the large gap before Explore AI-Generated Music, and consolidate tokens after separating residue from rendered styles.
Lacuna is visually stable for real mobile users, but interaction responsiveness is the material performance weakness. Field data records mobile p75 LCP at 1,986 ms and CLS at 0.03, while p75 INP is 506 ms in the poor band. The mobile lab run reached LCP at 3,676 ms, and sampled route transfers were 2,942 KB on the homepage, 2,949 KB on /ai-song-generator, and 3,120 KB on /stem-splitter. Named third parties account for at least 268 KB on the homepage. Profile the handlers behind INP first, then remove the estimated 135 KiB of unused JavaScript, defer non-essential measurement, and set route budgets near 200 KB compressed JavaScript and 1.5 MB mobile transfer.
Lacuna’s copy is most effective when it names a job and a workflow, and weakest when the directory repeats the same template. The homepage combines "AI Music Generator — Turn a Spark into Sound" with songs, lyrics, MIDI, and live coding; localized heading trees repeatedly use "AI Music Agent" and "AI Lyrics Agent". Sentence rhythm also slows comparison: mean sentence length is 24.2 words on /ai-song-generator, 29.1 on /ai-lyrics-generator, 30.4 on /midi-editor, and 46.1 on /pricing. Put the existing 120-credits-a-month and no-card-needed facts beside the pricing H1, give tool families distinct scenarios, split long benefit sentences, and complete the confirmed image-alt hygiene pass.
Lacuna’s pricing page contains real comparison detail, but it asks visitors to interpret the economics before explaining which plan fits their workload. Basic, Pro, and Ultra appear together with monthly/yearly context, and the "What your credits do" table contains 17 rows and 51 plan cells across generation and editing operations. Pro is marked Popular and described for regular creation, yet the page does not visibly explain why Basic or Ultra is preferable for different workloads or what tradeoff would justify overriding Pro. Keep the detailed table, add three workload-based recommendations with one reason and one tradeoff each, and lead with 8–12 decision-critical rows before progressively disclosing model-specific credit economics.
Lacuna’s sampled public surface is technically resilient, while the main uncertainty is measurement rather than an observed suppression defect. The 40-page sample returned 200, used index-follow directives and self-canonicals, and sat behind a verified sitemap; nonexistent URLs returned 404, HTTP redirected to HTTPS in one hop, and the non-www host consolidated to www HTTPS. Raw and rendered content were effectively identical, so no render-gap risk was observed for primary content or discovery. The crawl has no Google Search Console or analytics data, so traffic change cannot be diagnosed. Connect those sources, track high-value tool queries, and address the separately measured 506 ms mobile p75 INP without turning it into a traffic-loss claim.
Lacuna has a coherent marketing system, but the supplied evidence supports a medium-confidence editorial score because claim support, repetition, and mechanical hygiene are not fully gated. Homepage FAQ schema uses consequential wording such as generating a complete original song "in seconds" and providing "full commercial rights"; the supplied artifact does not show supporting source links or conditions, so these claims should be reconciled with visible copy and current terms. Localized heading trees repeat the same feature sequence. Sentence lengths reach 46.1 words on /pricing, while exact-match anchors occur 29 times each for "mp3 to midi" and "midi to mp3". Add source paths, distinct scenarios, sentence edits, title checks, and rendered-alt checks before publication.
Lacuna’s machine-readable product inventory is useful, but it does not replace task-level documentation. In contrast, /llms.txt, updated October 13, 2026, describes music, audio, stem, MIDI, and export workflows, and the homepage FAQPage covers ownership, credits, account requirements, vocals, and genres. Turn that inventory into a searchable human help center with getting-started guidance, task articles, troubleshooting, and escalation links. Keep /llms.txt synchronized as the AI-readable index, while linking each listed workflow to a canonical human-readable guide.
Lacuna’s technical SEO foundation is strong across the 40-page sample, with mobile interaction latency as the main measurable weakness. Sampled URLs returned 200, were index-follow, used self-canonicals, and appeared in the verified sitemap; robots.txt points to the sitemap containing 994 URLs. HTTPS, HSTS, and core security headers are present, and raw/rendered content is effectively identical. Homepage field data records p75 INP at 506 ms alongside LCP at 1,986 ms and CLS at 0.03. Profile main-thread JavaScript to improve INP, add concise or empty alt text appropriately, and run a broader crawl before making sitewide claims about internal-link depth, orphan status, or hreflang reciprocity.
Lacuna is a strong fit for people creating songs, lyrics, audio, and MIDI who want an end-to-end browser workflow. The site makes AI music creation clear, communicates a broad creation-to-editing capability, and pairs a 94/100 accessibility score with a 95.5/100 technical SEO score.
The next improvements are specific. Publish fuller public documentation beyond the existing machine-readable product inventory and homepage FAQ. Make the primary audience and commitment questions more explicit. Turn the feature-list comparison into clearer decision guidance, and tighten repeated or weakly supported marketing claims. Mobile interaction also needs attention: p75 INP is 506 ms despite good field LCP and CLS.
The product earns its strong verdict through breadth and a solid technical base. Its buyer experience will improve when the site explains who each workflow serves, how options differ, and where users can find detailed help.
This is a 13-dimension review based on a crawl of 40 pages completed on 2026-10-17. The article uses the supplied public dimension score table, current product facts, site profile, FAQ evidence, performance field metrics, and technical SEO checks.
The crawl records 13 · Review-content integrity as not applicable, so it has no article section. Google Search Console enrichment was not connected or accessible for this review. The supplied evidence also notes an llms.txt product inventory updated October 13, 2026, alongside the homepage FAQ; the low Docs & self-serve help score reflects the gap between that inventory and fuller public documentation.
See How SiteList scores for the scoring framework. Scores and measurements here are limited to the supplied crawl and enrichment state; they are not a guarantee of behavior outside the sampled pages or date.
You describe a musical vision or provide lyrics, and Lacuna's AI generates an original song with vocals, melody, harmony, and instrumentation.
Yes. Lacuna generates complete songs with AI vocals, and you can specify vocal style, gender, and tone.
Yes. New users receive free credits for their first songs, and no credit card is required to start.
Yes. You can remix or extend a track, or select a waveform section to rewrite while keeping lyrics time-aligned.
The site says generated tracks may be used commercially, with plan-specific conditions and a downloadable Pro license certificate; verify the current terms before relying on that right.