---
title: "Discussion on \"How to evaluate text-to-speech voices before you ship them\" | Hashnode"
description: "Discussion on \"How to evaluate text-to-speech voices before you ship them\". Comparing TTS voices with real scripts: first-byte vs total latency, a server proxy that hides the key, and Web Audio levels."
url: "https://hashnode.com/posts/how-to-evaluate-text-to-speech-voices-before-you-ship-them/6af2ce59a7f51641ecaeae20"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How to evaluate text-to-speech voices before you ship them](https://mahmadmanzoor.hashnode.dev/how-to-evaluate-text-to-speech-voices-before-you-ship-them?utm_source=hashnode&utm_medium=feed)

Comparing TTS voices with real scripts: first-byte vs total latency, a server proxy that hides the key, and Web Audio levels.

6d ago · 9 min read · mahmadmanzoor.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#text-to-speech](https://hashnode.com/tag/text-to-speech)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#audio](https://hashnode.com/tag/audio)

## Written by

[Muhammad Ahmad](https://hashnode.com/@mahmadmanzoor)

@mahmadmanzoor · Lahore, Pakistan

  
[View profile](https://hashnode.com/@mahmadmanzoor)

AI Product Engineer @ RipeSeed. Shipping LLM features, agents and evals in production.

## Responses 7

Markdown supported · ⌘↵ to post

[DemoVexa](https://hashnode.com/@demovexa)

[5d ago](https://hashnode.com/posts/how-to-evaluate-text-to-speech-voices-before-you-ship-them/6af2ce59a7f51641ecaeae20/comment/6af3d5aed6b5ade573041acf)

Two numbers instead of one is the part most voice comparisons miss. A voice that starts fast but finishes slowly feels fine in a chat and drags in a long narration. I'd add two things to the review step. First, match loudness before comparing takes, because the louder of two takes almost always sounds better on a quick listen, whatever the voice. Second, hide the voice name while listening and only reveal it after you've rated the row. Otherwise it's easy to end up confirming the voice you already liked on the provider's demo page. The getAll check for exactly one voicePreset is a neat catch, and moving voice IDs into a server allowlist closes a hole that most TTS demos leave open.

[DemoVexa](https://hashnode.com/@demovexa)

[3d ago](https://hashnode.com/posts/how-to-evaluate-text-to-speech-voices-before-you-ship-them/6af2ce59a7f51641ecaeae20/comment/6af3d5aed6b5ade573041acf#reply-6af73f4a3b7fa79a4a2fbe07)

Two people is a good size. It's enough to catch one person's habit, and small enough that you don't end up averaging the pick into a voice nobody really likes. When the two of you split on a voice, how do you break the tie? Play it for someone outside the team, or go with whoever owns the script?

[Muhammad Ahmad](https://hashnode.com/@mahmadmanzoor)

[1d ago](https://hashnode.com/posts/how-to-evaluate-text-to-speech-voices-before-you-ship-them/6af2ce59a7f51641ecaeae20/comment/6af3d5aed6b5ade573041acf#reply-6afa25aedcee6ad45966c6bd)

Usually whoever owns the script makes the call, since they know where it will be heard. If it's still close, we play both takes to someone outside the team with the names hidden.

[DemoVexa](https://hashnode.com/@demovexa)

[22h ago](https://hashnode.com/posts/how-to-evaluate-text-to-speech-voices-before-you-ship-them/6af2ce59a7f51641ecaeae20/comment/6af3d5aed6b5ade573041acf#reply-6afa6df727009a9f016d4d3b)

Letting the script owner decide makes sense, since they know whether it will play on a phone speaker or in headphones. A blind listen from someone outside the team is a clean tie-break too, because they have no favourite yet. Thanks for answering all my questions on this one.
