With Review: strong local TTS studio (76/100)

Quick facts summarize the reviewed site and crawl scope.

Field	Value
Domain	desktop.with.audio
Category	Local text-to-speech for desktop users
Pricing	Paid; starting at .99 for personal use
Pages crawled	36
Crawl date	2026-08-31

With is a strong, focused local text-to-speech studio for desktop users, scoring 76/100 overall. The public score table shows its clearest strengths in first impressions and positioning (92/100), usability (92/100), audience and messaging (87/100), and design execution (87/100). The site communicates a specific privacy premise and uses technically precise language for an audience that values control over its data.

The weaker areas are concrete. Writing quality scores 58/100, while decision-support surfaces score 10/100 because pricing pages yielded no extractable comparison content. Risk and stability and technical SEO each score 62/100; the crawl found a confirmed soft-404, duplicate titles across 32 pages, and client-side rendering on selected pages. Performance is still strong at 78/100, but the homepage’s main mobile content loads in 3.1 seconds and a 380KB hero image blocks rendering without a loading strategy. Documentation is a relative strength at 78/100.

WithAudio makes its offline-first position clear from the first screen. The hero claim, "Text to speech that never leaves your computer," is specific and testable, while testimonials with company attribution, technical blog posts about the MLX stack, and pricing at $9.99 for personal use give the promise useful support. The language is plain and technically precise for readers who value control over data. The remaining gap is competitive context: the site does not explain its position against named alternatives. Add a comparison page that states where WithAudio’s offline model differs and which users benefit most.

With answers the audience’s core questions about what the product does, what it costs, why privacy matters, and how to begin. Its language is technically precise without losing clarity, which suits desktop users who want local control of text-to-speech. Category-specific questions remain less developed, including data migration and integrations with other tools. Add an FAQ that addresses those workflows directly, including how an existing TTS setup can be moved and which integrations are supported. That would extend the current privacy-led message into a clearer fit assessment for enterprise users.

WithAudio’s visual hierarchy is clear, but its homepage does not provide a direct path to several key tasks. Pricing is absent from the main navigation and content area, so finding cost and plan fit takes three clicks through the footer: home → footer → pricing → pricing page. The contact page displays email addresses only, which makes contacting a human less direct for first-time visitors. Add a prominent Pricing link beside the main product links, place a "See Plans" or "Get Started" CTA above pricing content, and add an actionable contact method such as a form, phone number, or live chat.

WithAudio has a coherent visual system, consistent spacing, clear hierarchy, and a mobile layout with no horizontal scroll at 390px. The main mechanical gap is contrast: white text on the semi-transparent black CTA fill measures 2.8:1 in both the hero and pricing section, below the 4.5:1 WCAG AA requirement. Change the button fill to #4B5563, use a darker background, or apply the more saturated #f59e0b accent. Card padding and section margins show smaller variations, but contrast is the fix with the clearest accessibility impact.

WithAudio’s homepage remains strong at 78/100, but its mobile LCP is 3.1 seconds and the hero image is the clearest avoidable cost. The 1595px × 1065px image is 380KB, rendered at 990px wide, and has no loading or preload strategy. Add the appropriate image loading treatment and preload the hero asset with high priority. Google Tag Manager also loads synchronously and contributes 843KB of blocking JavaScript; defer it or remove non-essential third-party code from performance-critical pages. The community image is 844KB at source size and lacks width and height attributes.

WithAudio has a strong privacy-led voice, but the homepage asks one extracted paragraph to carry 804 words. The feature sequence—Chrome companion, batch and audiobook exports, and auto-scroll and highlighting—would be easier to scan as short blocks or cards. Several public product routes also have no H1, while the homepage has two, weakening page-level clarity. Documentation is task-shaped, but the quick-start copy includes "Purchase and active the licence" and "own it for ever." Split the homepage copy, give each route one descriptive H1, and proofread the setup instructions while preserving the direct tone.

WithAudio’s decision support is currently unverified and scores 10/100 because the pricing surfaces expose no extractable comparison content. The crawl captured only the title "Desktop WithAudio" at /pricing, /ios/pricing, and with.audio/pricing; no feature rows, pricing cells, or comparison grid were captured. Make the pricing tables visible in the initial DOM or server-render them, then add a concise recommendation such as "Best for X" beside each tier. Buyers need both the numbers and a clear explanation of which option fits their use case.

WithAudio’s clearest stability risk is indexability: a guaranteed-nonexistent path returned HTTP 200 with the product page, creating a confirmed soft-404. Selected pages also depend heavily on client-side rendering. The download page contains 2 raw words versus 199 rendered words, with a client-side share of 0.965. Return HTTP 404 for nonexistent paths and verify the probe after deployment. Then move primary content into the initial HTML for the affected template so the page remains understandable when rendering is limited. No traffic decline is established by the supplied inputs.

With’s documentation is a strong self-serve resource at 78/100, with task-based guides for local model runtimes, license transfers, document handling, and troubleshooting. Search and sidebar navigation are present. Separately, /llms.txt served an HTML response in the supplied probe; this result should be treated as a route-level observation, not as a broader failure of the documentation.

WithAudio has sound crawl basics, including HTTPS redirection in one 301 hop, permissive robots directives, and sampled nosniff responses. Technical SEO still scores 62/100 because a guaranteed-nonexistent path returns HTTP 200, the title "Desktop WithAudio" is shared by 32 pages, and selected templates depend on client-side rendering. The download page has 2 raw words and 199 rendered words; the iOS languages page has 2 raw words and 179 rendered words. Return 404 for unknown paths, give each indexable page a unique descriptive title, render primary content in initial HTML, and choose one trailing-slash policy for /roadmap.

With earns its strong 76/100 verdict through focused positioning, clear audience fit, strong usability, and a coherent visual system. It is best suited to technical desktop users who want local text-to-speech and value privacy and control over their data.

The next improvements are straightforward: expose usable comparison content on the pricing surfaces, deepen and tighten the homepage writing, and resolve the confirmed soft-404 and duplicate titles across 32 pages. With has a credible foundation; its public decision path and crawl-visible technical details need to catch up.

This is a 13-dimension review based on a crawl of 36 pages completed on 2026-08-31, using the public dimension score table and its one-line summaries. The review covers positioning, messaging, usability, design, performance, writing, decision support, risk and stability, documentation, and technical SEO among the dimensions with supplied public evidence.

Dimensions 04 · Accessibility and 13 · Review-content integrity were marked not applicable. Dimension 19 · Editorial QA of content was excluded because evidence was missing. Search Console access was not connected, so traffic-loss diagnosis was not possible. Pricing surfaces also yielded no extractable comparison content, likely because they are client-side rendered. Read more in How SiteList scores.